Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.234 ·

/tui and /update refuse to restart when session state would be lost, and say what is holding them up

/tui and /update now refuse to restart when it would lose session state, naming the exact blocker.

You'll notice New Features
JSON All of v2.1.234
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Slash CommandsArea: what it touches
New FeaturesKind: in v2.1.234,
What probably matters to youSection of the release
What

Before relaunching, both commands check for state that cannot be reconstructed from a restart command line: permission rules that exist only for this session, ask rules with no command-line equivalent, added directories that cannot be spelled out, and a running auto-reply monitor for artifact comments. Instead of the old generic "busy" message, they name the specific blocker and tell you what to do about it. /tui saves your renderer preference but stays where it is; /update tells you to exit and start claude again yourself.

Details
  • When the blocker is uncarriable session state, the refusal explains it is holding back because there are permission rules a command line cannot carry intact.
  • When the blocker is the artifact comment monitor, /update refuses with "Can't restart while auto-replying to artifact comments" and /tui with "Cannot switch renderers while auto-replying to artifact comments", both pointing you at /tasks to stop it.
  • The "saved without restart" confirmations gained matching comment-monitor wording so the reason is visible there too.
  • The tengu_update_refused and tengu_tui_refused telemetry events gained fields for what was uncarriable, a comment_monitor field, a deferred field, and a count of active tasks in a field that previously held only a yes/no.
Evidence

permission rules a command line cannot carry intact, Can't restart while auto-replying to artifact comments

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Read from
Names in the bundle/tui/update
Since it was published

The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.

Confirmed since Anthropic's documentation has since written up /tui, on Claude Code changelog. * Fixed `/tui` refusing to restart because of an agent-team teammate that had already finished its work and was no longer shown in the agents panel changelog see the edit
Added since A small documentation edit on Error reference touched a line naming /tui after this was published. These errors come from the `claude` command line and its subcommands, from a command name you submit at the prompt, and from commands such as `/security-review` that gather context by running shell commands before their prompt runs. They a… errors see the edit
Confirmed since Anthropic's documentation has since written up /update, on Update Service Account. url: https://platform.claude.com/docs/en/api/beta/organization/service_accounts/update api/beta/organization/service_accounts/update see the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /update, on Update Service Account.
Anthropic's release notes agreeFixed /tui dropping launch --allowed-tools/--disallowed-tools rules when it restarts; it now declines to switch, with the reason, when the…

See this entry in the whole of v2.1.234 →

Feedback