You'll notice
Useful3 Signal3
MCP and OAuth error text is redacted when your session runs off your machine.
What's wrong with this entry?
Anonymous. No account, no email.
/mcp
What
Failures from MCP servers and OAuth flows no longer echo raw exception text when the session lives off your machine. Reconnect, enable and disable actions in the /mcp server views, MCP calls, MCP authentication, MCP OAuth callback URLs and the Claude OAuth callback all return a redacted message instead, and the real error text is written to the local debug log. A normal local run is unchanged and still shows the full error.
Details
- Covers the stdio and remote server detail views and the reconnect action, which reports
Error reconnecting to ${St(o)} (detail withheld on this connection). - Control-channel responses substitute
(detail withheld)for the underlying message. - Redaction over the control channel is gated on the environment variable
CLAUDE_CODE_ENVIRONMENT_KINDbeing set tobridgeand on the connection persisting off the machine; otherwise the raw error is passed through as before. - The
/mcpview redaction has no flag of its own and follows solely from whether the session persists off-box. - Server names, messages and modes are sanitized before being interpolated into any response.
- MCP and OAuth failures are routed through one shared error responder rather than stringifying the exception at each call site.
Evidence
Error reconnecting to ${St(o)} (detail withheld on this connection)., (detail withheld)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.