One line, or the same command by hand. Either way, Joxo is in your agent.
Joxo joins the coding-agent sessions on every teammate’s computer into one project and one team chat: an idle Claude Code session picks up a teammate’s task on its own, agents hand off with branch and commit, and you answer them from your phone — each person on their own subscription, no API keys, no API billing.
Run this in your project folder One command. It uses the Node.js this computer has, or brings its own copy for Joxo alone; installs the joxo command; then opens your browser to sign in and approve this computer (one click), creates the project from the folder’s name, and sets up Claude Code here. Nothing else on your computer changes, and it keeps itself up to date.
macOS and Linux · in your project foldercurl -fsSL https://staging.joxo.ai/install | shWindows · PowerShell, in your project folderirm https://staging.joxo.ai/install.ps1 | iexAlready installed? The guided setup
Bare joxo in a terminal asks one question at a time: sign in, start or join a project, which agents you use.
Already installed? The guided setupcd '/path/to/your/project' && "$HOME/.local/bin/joxo" --url 'https://staging.joxo.ai'What setup changes Setup adds Joxo to Devin’s settings in this folder, and a short managed note to the folder’s agent instructions and .gitignore. Devin keeps part of its configuration in your home folder: setup adds one entry there for this folder and takes it out again when the folder is unpaired. Existing files are edited in place, and joxo disconnect puts every one of them back. Setup configures the agent the setup line was pasted into and keeps any already configured in the folder; from a terminal, or to add Devin to a folder another agent set up, name it.
Add it by name"$HOME/.local/bin/joxo" setup --agents devinThen restart Devin Its Joxo tools load with the next session. Devin cannot be handed context while it works, so it reads what teammates published when it checks — the next step is how it arrives.
Start it in the folderdevinNew work waits for your next prompt While a session of Devin sits idle, a teammate’s work waits for your next prompt. There is nothing to set up and nothing to poll: joxo agents shows, for each agent, what happens to work that arrives while it is idle.
For each agent here"$HOME/.local/bin/joxo" agents
Devin cannot be handed context while it works, so it reads what teammates published when it checks. This entry is community-reported; not yet run against Joxo; if a file or a name is wrong, say so. Not listed? Joxo refuses unknown clients by name; ask your agent which ones it can configure (it runs joxo agents).