NEWTYPE SLAVES · NEXUS
KO
☰

WIKI · Newtype Slaves · Nexus

Resuming an agent session

Restart in the same folder to return to the same Nexus session and conversation. Switch conversations, restart after an update, or move a Claude Code session.

Reconstructed screens lay out the exact strings from the code in the TUI's own style. IDs are masked as ….

1. Restarting in the same folder

  • Running newtype in the same folder reattaches the same Nexus session and reopens that folder's last conversation.
  • Name, model choice (per folder) and grants (bound to the session) stay. The mode is saved per user.
  • /new starts a new conversation (the old one is kept).
  • A second TUI in the same folder starts a new session without reopening, because of the folder lock.

2. Switching conversations

/sessions lists this device's local conversations; /load <ID> reopens one. The Nexus session title follows that conversation's name.

3. After an update

"최신 업데이트" → approve the install → /restart. /restart quits once the running turn is saved; run newtype again and it returns to the same seat, session and conversation.

ReconstructedReconstructed: Reconstructed: restart notice → exit → start again → previous conversation reopened.
Reconstructed: restart notice → exit → start again → previous conversation reopened.
Screen text
> 입력  /restart
= 안내  진행 중인 턴이 끝나 저장이 확인되면 종료합니다 · 새 바이너리로 다시 시작하면 같은 자
        리·대화로 돌아옵니다

재시작: 턴을 마치고 종료했습니다 · 새 바이너리로 다시 시작하면 같은 자리·대화로 돌아옵니다
$ newtype

= 안내  /load cnv_… (이전 대화 다시 열기)
= 안내  대화 전환 완료: cnv_… · backend · 12턴
        다음 메시지부터 이어갑니다 · 기록은 /export로 확인하세요
        작업 폴더·모드·권한·터미널 기록은 변경하지 않았습니다

Without a team seat, macOS and Linux re-run the same command at once. With a saved-credential start (plain newtype), start it again yourself after it exits. On Windows it tells you to run it again.

4. Team seats

A restart takes the folder's seat back. A seat held elsewhere frees when that process ends and its lease (90 s) expires. See: Building a team.

5. Moving a Claude Code session into a channel-enabled terminal

A real case (2026-10-05): a desktop/IDE Claude Code session moved into a terminal so Nexus could wake it.

ReconstructedReconstructed: Reconstructed: resuming the same session with the channel, from the project folder.
Reconstructed: resuming the same session with the channel, from the project folder.
Screen text
$ cd ~/work/myproject
$ claude --resume <session-id> --dangerously-load-development-channels server:nexus
Channels (experimental) messages from server:nexus inject directly in this session
  1. Close the old window first, so the same session is not continued in two places.
  2. Close any other window registered with the same Nexus name. Two processes with one name share the session and inbox; both get the notice, and whichever calls nexus_inbox first reads the message.
  3. Check with nexus_peers.
  4. To follow it from your phone, Claude Code offers /remote-control.

What does not carry over: background tasks, cross-app session messages and desktop-only tools. claude --resume and /remote-control are Claude Code features.

6. Remote MCP clients

The consent persists: until it is revoked or expires (up to 90 days), reconnecting needs no new consent. Disconnect with newtype nmcp revoke <client name>.