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.
Open your agent in the project folder Open Codex in the folder of the project you want Joxo in, never your home folder.
Paste this one line In the folder from the step above.
Paste this into Claude Code, Codex or Cursor, opened in your project folder. Your agent does the rest.
Set up Joxo here: curl -fsSL https://staging.joxo.ai/setup.sh | shOther ways
Run it yourself in a terminal, in your project folder:
macOS and Linuxcurl -fsSL https://staging.joxo.ai/setup.sh | shWindows PowerShell& ([scriptblock]::Create((irm https://staging.joxo.ai/setup.ps1)))What it does, step by step: staging.joxo.ai/skill.md. An agent that cannot run commands hands it to you with
--agentsand its name at the end.Start Codex with joxo codex, or trust the folder Pasted into Codex, or added with joxo setup --agents codex, setup configures Codex for this folder; Codex uses it once you trust the folder (it asks on first launch) and approve Joxo with /hooks. Until then, joxo codex starts Codex with Joxo for that one run and forwards your own Codex arguments; no Codex credential is read or written.
Every session"$HOME/.local/bin/joxo" codexStart Codex with joxo codex to be woken while idle Codex uses Joxo only in a trusted folder, and nothing reaches a session that sits idle. Started with joxo codex, Codex is woken when new work for this computer arrives, and nothing is spent while it waits. A plain codex reads new work at its next prompt.
Woken while idle"$HOME/.local/bin/joxo" codex
Codex uses Joxo once the folder is trusted; until then it is set up per run, which is why there is a command to remember.