Set up JupyterLab on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/jupyter.md from top to bottom. The recipe's example VM name is my-jupyter. This VM's name is the output of `hostname`: use it wherever the recipe writes my-jupyter. Skip the step that creates the VM; you are on it. You are done when all of these are true. Check each one yourself: - JupyterLab at your VM's private URL, signed in with exe.dev. No token or password. - A Python 3.13 kernel with pandas and matplotlib, plus a recipe for more environments. - Claude, Codex, and Jupyternaut in the chat panel; Claude edits and runs your notebooks. - Model calls from notebooks with the OpenAI SDK, without an API key. - Real-time collaboration, so edits by agents and teammates show up as they happen. - Starts again after a reboot; nightly backups of notebooks, chats, and package lists. Read the whole recipe, including the closed details. For initial setup, follow "Install by hand" first, skipping VM creation and SSH: JupyterLab, the data kernel, the config, the service, the checks, the AI agents, the backup timer, and the backup check. Those checks are enough; don't install extra tools or browsers to test further. The walkthrough at the top is for the owner afterwards. Do not run Restore, Update, "Add another environment", or JupyterHub. Work as exedev. JupyterLab serves port 8000, the VM's main proxy port. Don't share the VM, and never make it public. Leave Jupyter's token on; never print it in your reply. Keep test prompts to a word or two. Delete the check notebook afterwards. Verify jupyter.service is enabled; do not reboot. Finish by giving the owner https://.exe.xyz/. Finish with the URLs I should open and these commands, which only I can run, from my own computer (with this VM's name in them): ssh exe.dev share add my-jupyter teammate@example.com