{"version":"2.1.234","anchor":"tui-and-update-refuse-to-restart-when-session-state-would-be","canonical_anchor":"tui-and-update-refuse-to-restart-when-session-state-would-be","heading":"\/tui and \/update refuse to restart when session state would be lost, and say what is holding them up","tier":"notice","area":"Slash Commands","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/tui-and-update-refuse-to-restart-when-session-state-would-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### \/tui and \/update refuse to restart when session state would be lost, and say what is holding them up\n\n\/tui and \/update now refuse to restart when it would lose session state, naming the exact blocker.\n\n**What**\n\nBefore 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.\n\n**Details**\n\n- 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.\n- 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.\n- The \"saved without restart\" confirmations gained matching comment-monitor wording so the reason is visible there too.\n- 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.\n\n**Evidence**\n\n`permission rules a command line cannot carry intact`, `Can't restart while auto-replying to artifact comments`\n\n- Area: Slash Commands\n- Names: `\/tui`, `\/update`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}