Runner 0.7.0
Fork a chat into a new tab
Fork any claude-code or codex chat — from the chat header's ⑂ button, or the sidebar tab's ⋯ → Fork chat. The fork opens in a new tab titled <source> (fork) with the full conversation history; the source chat is never touched, so you can fork one mid-turn while it keeps working.
- Fast: forks open at CLI-boot speed on both runtimes. Codex captures the new session key in a ~0.2s headless step; claude forks spawn directly with an assigned session id.
- Fork controls are disabled with an explanatory tooltip where forking isn't possible (TRAE chats, or a chat whose session key hasn't landed yet).
- Each fork logs a one-line timing breakdown (
fork timing:) for observability.
Known behavior
- A codex fork briefly shows a "Conversation interrupted" banner at the top — cosmetic, left by the key-capture step.
- A claude fork you never type into isn't durable yet (claude only materializes the conversation file on the first message): stop and resume it untouched and it comes back empty. Type anything and it's permanent. Codex forks are durable from birth. Re-fork the source to recover.
Docs
- Feature specs now carry their GitHub tracking-issue number (05→73, 58→393, 61→403);
docs/anddocs/impls/gained index READMEs.
Full changes: https://github.com/yicheng47/runner/commits/v0.7.0