Resuming threads

Every Magic Coder session is a thread. A thread is a conversation — your messages, the agent’s replies, the tool calls, and the model and settings used along the way. Threads are stored in BridgeApp, which is why you can resume one from a different machine.

When you exit, you get a thread ID

When a session ends with a resumable thread, Magic Coder prints something like:

Continue on any device:
coder --continue 8a3f2b1e-4d6c-4e9f-9b2a-c12345678abc

Save the UUID. It’s how you re-open the thread later.

Resuming an existing thread

coder --continue 8a3f2b1e-4d6c-4e9f-9b2a-c12345678abc

A few things to know:

• You don’t need to pass --cwd if you’re resuming from the same machine — the working directory associated with the thread is reused.
• If you’re resuming on a different machine, run the command from inside the relevant repo; Magic Coder reconciles the working directory with the thread’s expectations.
• Sign-in must already be saved on the resuming machine (run coder once interactively first if not).

Resuming on a different device

The conversation history lives in BridgeApp, so any machine where you’ve signed in to your BridgeApp account can pick up a thread. Useful patterns:

• Start a long-running investigation on your dev workstation, jump to your laptop while traveling, finish the task there.
• Keep a thread running through the day across SSH sessions on different boxes — same thread, same context.
• Hand off a thread to a teammate by sharing the UUID. They’ll need access to the same BridgeApp workspace and a checkout of the same repo.

The thread carries the conversation. Local state — file edits, trust decisions, remembered command-permission choices — lives on each machine. Granting trust on the new machine is a one-time prompt.

Combining —continue with other flags

--continue is the startup target. You can combine it with:

• --query "<follow-up message>" — resume and immediately send a new message.
• --model <name> — switch the model for the resumed thread.
• --reasoning-effort <level> — change reasoning effort.
• --allow-long-context — turn on long context for this run.
• --plan — flip into plan mode for the next message.
• --automagic (with --trust) — resume hands-off and run a follow-up to completion.

Example: resume on your laptop and ask for a follow-up under higher reasoning effort:

coder \
  --continue 8a3f2b1e-... \
  --reasoning-effort high \
  --query "now also update the integration tests"

Starting a clean thread inside a session

If you’re inside the TUI and want to start a fresh conversation in the same workspace without exiting:

/clear

(Or /reset — same thing.) That ends the current thread and starts a new one in place. The thread you cleared remains resumable by UUID if you saved it; otherwise it’s gone.

Finding past threads

Today, the canonical place to find your threads is BridgeApp itself — the conversation history lives there alongside the rest of your account. The TUI prints a --continue hint at exit; outside that hint, you’ll go to BridgeApp to browse, search, or rename threads. A richer thread browser inside the TUI is a future addition.