When /update or a restart is refused, for example because the session was resumed from a different project directory or a background task is running, the message no longer checks whether an artifact 'comment monitor' task is active and no longer adjusts its wording for that case. The messages for transcript-path drift and for background tasks running are now fixed text, without the earlier note that restarting would stop auto-replies to artifact comments.
Why
The refusal messages are simpler and no longer vary based on whether artifact comment monitoring happens to be running, so the caveat about losing auto-replies to comments is no longer shown even if that monitoring is active.
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.
Added sinceA small documentation edit on Commands touched a line naming /update after this was published.| `/update-config [request]` | **[Skill](/docs/en/skills#bundled-skills).** Describe a settings change, such as allowing a command, setting an environment variable, or adding a [hook](/docs/en/hooks), and Claude edits the matching [`settin…commandssee the edit
Confirmed sinceAnthropic's documentation has since written up /update, on Claude Code changelog.* Fixed `/update-config` writing `Write(path)` permission rules, which file permission checks don't match, instead of `Edit(path)` ruleschangelogsee the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtNothing has been read yet about the `tengu_update_refused` or `tengu_update_bg_respawn` gates mentioned alongside this change.
Anthropic's documentation agreesAnthropic's documentation has since written up /update, on Claude Code changelog.
