Skip to content

site: home story gains a chapter, a restart doesn't end the session - #177

Merged
harshalgajjar merged 2 commits into
mainfrom
site-restore-chapter
Oct 6, 2026
Merged

harshalgajjar merged 2 commits into
mainfrom
site-restore-chapter

Conversation

@harshalgajjar

Copy link
Copy Markdown
Owner

Adds a seventh chapter to the home page's scroll story, before the agent bus, showing session restore (shipped in 3.15.0). Harshal reviewed it on a reminal expose preview and approved it.

Copy

A restart doesn't end the session. When a machine reboots, crashes or loses power, every session that was running comes back when you log in: the same link and PIN, what was on screen, and a shell in the folder you were working in.

Your agents come back too, on the same conversation. Claude Code, Codex, Gemini, Qwen, Cursor, OpenCode and pi pick up where they left off, with the options they were started with. A session you ended yourself stays ended.

This follows changelog/3.15.0.md.

Scene

  1. studio-mac runs Claude Code, Codex and a dev server, each showing its session link ID.
  2. It restarts: the card says "restarting", the sessions grey out and the terminal goes dark.
  3. It comes back "online · back": each session reappears at the same link ID, with a "same link · same PIN" tag.
  4. Claude's terminal shows its old screen dimmed, then the restore banner and the resume command exactly as internal/client/restore.go writes and types them (── reminal restored this session after its machine restarted ──, then claude --resume <id> at the prompt). Claude carries on.

Checks

  • All seven chapters play at 1280px and 390px, with no script errors and no horizontal overflow. (Locally the only failed request is /ping, which only the Worker serves.)
  • go test ./site/ passes.
  • No new em dashes. The one em dash on the page is the hero terminal's real CLI banner. The ones in the restore banner are box-drawing characters, as the CLI prints them.

Merging this only changes the repo. reminal.app updates on the next site deploy.

🤖 Generated with Claude Code

harshalgajjar and others added 2 commits October 5, 2026 20:27
A seventh chapter, before the agent bus: a machine running Claude Code,
Codex and a dev server restarts; when it is back each session reappears
at the same link, and Claude's terminal shows the old screen, the restore
banner and the resume command exactly as restore.go writes and types
them, then carries on. Copy from the 3.15.0 notes: sessions come back
with the same link and PIN, what was on screen, a shell in the folder;
Claude Code, Codex, Gemini, Qwen, Cursor, OpenCode and pi resume the same
conversation with their options; a session you ended stays ended.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
From the Open Source review against internal/client/restore.go:
- Claude Code, Codex, Cursor and Qwen are resumed by conversation id;
  Gemini, OpenCode and pi resume their latest. The copy now says agents
  come back 'picking up their conversation', which is true of both.
- Session ids are 8 characters from ABCDEFGHJKLMNPQRSTUVWXYZ23456789
  (internal/session/id.go). The scene's ids are now valid ones, and so is
  the example id 7F3A2C9E used by the hero terminal and the other scenes
  on home and /agents (it was lowercase hex everywhere).
- restore types Claude's full conversation id, a UUID; the scene shows one.
- Only coding agents are resumed: the dev server's session comes back as a
  shell in ~/app, not running.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@harshalgajjar
harshalgajjar merged commit 5cf0214 into main Oct 6, 2026
3 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 6, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant