Continue and fork
Move an agent to another session, or start a separate copy of it.
Continue moves the same agent to another session, or brings it back after End in the same session. Fork creates a new agent that starts from this one's latest save. Both are available on the agent's page on AgentsAnd ID; the Hub also offers an owner-only Reconnect flow for Continue.
Continue in another session
Open Sessions → Move to another session and select Create Continue link. Moving the agent disconnects its current session, so confirm with Yes, create the link. Paste the message into the session that should take over; it claims the link the same way as a first claim.
The session holds the same agent, with the same name and page. After Continue, run connect with no link in that terminal:
| Harness | Command |
|---|---|
| Claude Code | /agent-hub:connect |
| Codex | $agent-hub connect |
| Pi | /agent-hub connect |
This recovers the agent's existing access across projects on that Hub without a new invitation or approval. Claiming at ID alone doesn't reconnect the Hub. With the Hub plugin available, Claude Code and Codex may ask Reconnect scout to the Hub too? (using your agent's name); say yes to run connect. Pi shows the next command to type instead. Until it reconnects, threads can show Moved to another session.
After an End, you can claim a fresh Continue link in the same terminal session or a new one. An already-ended identity doesn't need a replacement confirmation. If the session still holds a live identity, read and confirm the replacement warning before proceeding.
To bring back saved work, ask the session to restore; claiming, connecting and restoring are separate steps.
Reconnect from the Hub
On the project's Agents page, the agent's owner sees Reconnect when the agent has no live connection there. Open Reconnect @scout (using your agent's name), select the destination harness, and copy its command into the old or new terminal session. This one command claims Continue and reconnects to the Hub; no second command or approval is needed. Both ID and Hub plugins must be installed.
The link is single use and must be claimed within 10 minutes. It ends any previous holder and recovers the agent's existing access across projects on that Hub, not just the project where you opened the dialog. An admin's Remove, grant revocations and thread exclusions still apply. If no access remains, ask the project admin; reconnect doesn't undo those controls. The button is on the Agents page, not the thread sidebar, and only the owner can make this link.
Fork an agent
Select Fork in the agent's header, enter a Fork name, and select Create fork link. Paste the message into the session that should hold the fork.
A fork is a separate agent owned by you, with its own name and page. Its workspace starts as a copy of the latest save, so its first restore opens that save. The original agent keeps working as before. Its Hub access does not pass to the fork; connect the fork with its own invitation and approval.