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.
Joxo serves three clients Claude Code and Codex run on your own computer and Joxo configures them completely; ChatGPT connects by URL. Every other MCP client is refused by name when it connects, rather than being served half a product — the relay names the three in its refusal and publishes the same list on /api/health.
Why refused rather than supported Joxo delivers a teammate’s work into a session as it arrives, which is hooks, and it hands work to a computer that can run it, which is a paired machine. A client with neither gets tools that read a project and nothing that makes Joxo worth having. Serving it would mean advertising a product that silently does a third of what the page promises.
If you want Joxo where you are Use the ChatGPT tab for a client that takes a URL, or the Claude Code and Codex tabs for a computer that does the work. If the client you have is one of those three under a name Joxo has not seen, it says so when it connects and names the variable that fixes it.
Joxo’s agent surface serves the three above. Another client is refused by name rather than half-working.