Remote handoff

Use /detach <host> in chat to continue the current conversation on a registered SSH server. You can send it while Jazz is working. Once the current turn finishes, Jazz prepares the handoff; it does not move a tool call that is still running.

/detach nightbox

Jazz asks what to continue doing, then shows the files, credential, and run limits for you to review. After you confirm the transfer and the remote run starts, the local chat closes. You can close your laptop and let the server continue.

Run this from the root of a Git repository. If messages are queued after /detach, clear or send them before transferring the conversation. You can also use /detach between turns.

Set up a server once

You need:

• An SSH alias in ~/.ssh/config that connects with a key, no password prompt, and whose host key is already in known_hosts.
• A Linux or macOS server (x64 or arm64) with curl and gzip, and an empty directory for Jazz to work in.
• An agent on a cloud provider: OpenAI, Anthropic, Gemini, OpenRouter, xAI, Cerebras, DeepSeek, Fireworks, Groq, Mistral, OrcaRouter, or Together AI. Local model servers do not travel.

Register the server and check it:

jazz hosts add nightbox nightbox /home/you/jazz-work
jazz hosts doctor nightbox

Jazz installs the Jazz release that matches yours into ~/.local/bin on the server the first time you detach. You do not install it by hand.

Your provider key goes into the server’s OS keyring. Most headless Linux servers have none, and the handoff stops with a hint to install libsecret. To keep the key in a private file (~/.jazz/secrets.json, mode 600) instead, register the server with the flag:

jazz hosts add nightbox nightbox /home/you/jazz-work --allow-file-secrets

Remote run limits

The server uses a low-risk approval policy with a $5, 8-hour, 100-iteration cap. Actions such as writing a file pause for your approval. Jazz prevents the conversation from running locally until you reclaim it.

Watch and steer it

jazz detach attach <handoff-id>

Attach replays everything the server has done, then follows it live. When a turn finishes, type your next message. When the run pauses for approval, answer y or n. An empty line or Ctrl+C leaves; the server keeps going, and attaching again picks up where you left off.

Take it back

jazz detach reclaim <handoff-id>

The server stops owning the conversation and never runs it again. Jazz applies the server’s file changes to your working tree and restores the conversation, remote turns included. Continue it with /resume in chat.

If a file changed both on your machine and on the server, reclaim writes nothing and lists the files. Commit or stash your edits and run it again, or let the server’s version win:

jazz detach reclaim <handoff-id> --overwrite

What moves with it

An agent’s custom tools move too, but they run their commands on the server, so the server needs those commands installed.

When something goes wrong

• unknown status. Jazz could not reach the server. The run may still be going; check again later.
• “This host has no OS keyring”. Install libsecret on the server, or re-register it with --allow-file-secrets.
• Nothing happens after a server reboot. The Jazz daemon does not restart on its own: ssh nightbox '~/.local/bin/jazz daemon'.
• “Conversation … is remote for host …”. That conversation is on a server. Reclaim it first.
• “A different skill already exists on this host”. Another handoff put a skill with the same name but different contents on the server. Rename one of them.

For the credential and isolation model, see Detach hosts.