What
A rename that applied locally but failed to reach the shared record of running sessions now says so, and points you at --debug for the cause. It used to fail silently apart from an unrelated line about a PID file.
Details
- The rename result appends the caveat only when the shared record was not updated.
- Also fixes a case where the confirmation printed the internal result object instead of the new name.
Evidence
Other sessions may still show the old name: the session registry could not be updated (run with --debug for the cause), applied locally but the session registry record was not updated
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundle--debug
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 --debug, on Hooks reference.
Hook execution details are written to the debug log file. Start Claude Code with `claude --debug-file <path>` to write the log to a known location, or run `claude --debug` and read the log at `~/.claude/debug/<session-id>.txt`. The `--debu…hooks see the edit
Added since
A small documentation edit on Channels reference touched a line naming --debug after this was published.
* **`curl` succeeds but nothing reaches Claude**: run `/mcp` in your session to check the server's status. A `failed` status usually means a dependency or import error in your server file. To see the stderr trace, restart with `claude --de…channels-reference see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Channels reference touched a line naming --debug after this was published.