Restarting via /update or /tui now carries your conversation over explicitly and says so if the restart fails.
tengu_hover_rest Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.234: on
Read once, for one account on one subscription tier, against v2.1.234. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
/update, /tui and the handoff to the desktop app now snapshot the conversation under a named handoff before restarting, so the transcript is carried across rather than picked up by chance. A restart that fails now says so inline instead of leaving the session in limbo.
- Handoffs are named "relaunch" and "desktop_handoff", and the storage handle is passed into the relaunch.
- The message on failure begins "Couldn't restart Claude Code — ".
- The plain-file half of this is active for everyone on this build; the storage-backed half only runs when the
tengu_hover_restflag is on, which it is not by default here.
Couldn't restart Claude Code —
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.246
Opus 4.8 hands off to a fresh session much earlier
Both mention handoff
-
v2.1.229
Command-sourced plugins are not rebuilt behind your back
Both mention update
-
v2.1.246
claude plugin updateaccepts a bare plugin nameBoth mention update