JoxoSETUP
PICK YOUR AGENT

One paste, or the same commands by hand. Either way, Joxo is in your agent.

Joxo joins agent sessions running on different computers so they can split the work between them. When one hits a usage limit the work hands off to another connected computer with the context intact, and hands back when the limit resets.

Claude CodeCodexChatGPTOther clients
  1. Install the connector

    Needs Node.js 22.13 or newer. It downloads one file to ~/.joxo/bin and leaves three shims — joxo, juncto and sync-work — in ~/.local/bin; nothing else on the machine is touched. It prints the PATH line for that directory but edits no shell profile, which is why every command below names the shim in full.

    01 · Install Joxo
    joxo_installer="$(node -e 'fetch(process.argv[1]).then(r=>{if(!r.ok)throw Error(r.status);return r.text()}).then(t=>process.stdout.write(t)).catch(()=>process.exit(1))' 'https://joxo.ai/install.sh')" && sh -c "$joxo_installer"
  2. Create your account

    Prints your personal sign-in link once. Keep it somewhere private — it is how you sign in from another browser or computer, and it cannot be recovered.

    02 · Create your account
    "$HOME/.local/bin/joxo" account create --name 'Your name' --url 'https://joxo.ai'
  3. Create the project and pair this folder

    One command creates the project, pairs this computer to it, installs Joxo into the folder and starts listening. Give it the project folder, never your home directory.

    03 · Create the project and pair this folder
    "$HOME/.local/bin/joxo" project create 'Your project' --dir '/path/to/your/project' --url 'https://joxo.ai'
  4. Start Codex with joxo codex

    Codex reads neither .mcp.json nor .claude/settings.local.json, so there is nothing to restart it for. joxo codex hands Codex the MCP server for that one run and forwards your own Codex arguments; no Codex config or credential file is read or written.

    Every session
    "$HOME/.local/bin/joxo" codex
  5. On Windows, run these three instead

    install.ps1 leaves the shim at $HOME\.local\bin\joxo.cmd and writes no extensionless joxo, so the commands above cannot run in PowerShell.

    Show the PowerShell commands
    Windows · 01 · Install Joxo
    node --input-type=module -e 'import {writeFile} from ''node:fs/promises''; import {join} from ''node:path''; const temp = process.env.TEMP; if (!temp) throw new Error(''TEMP is not set''); const r = await fetch(''https://joxo.ai/install.ps1''); if (!r.ok) throw new Error(''HTTP '' + r.status); await writeFile(join(temp, ''joxo-install.ps1''), await r.text());'; powershell -NoProfile -ExecutionPolicy Bypass -File "$env:TEMP\joxo-install.ps1"; Remove-Item -ErrorAction SilentlyContinue "$env:TEMP\joxo-install.ps1"
    Windows · 02 · Create your account
    & "$HOME\.local\bin\joxo.cmd" account create --name 'Your name' --url 'https://joxo.ai'
    Windows · 03 · Create the project and pair this folder
    & "$HOME\.local\bin\joxo.cmd" project create 'Your project' --dir 'C:\path\to\your\project' --url 'https://joxo.ai'

Codex is set up per run rather than per project, which is why there is a command to remember instead of a restart.