You'll notice
Useful2 Signal3
On remote sessions, MCP reconnect errors show a generic note and log the detail locally.
What's wrong with this entry?
Anonymous. No account, no email.
What
When you reconnect or enable/disable an MCP server from /mcp on a session whose connection persists off this machine, the underlying exception is no longer shown. You get "Error reconnecting to <server> (detail withheld on this connection)." and the real text is logged locally instead.
Details
- Every server name passed into user-visible text now goes through a sanitizing transform, and the completion callback is wrapped so it applies the same transform.
- Enable/disable failures pass a hint about whether the change persists off the machine into the failure-message builder.
- Local sessions are unaffected. The check that selects the withheld wording is a predicate applied to the session host; which sessions it matches is not decided in this code path.
Evidence
Error reconnecting to ${St(J)} (detail withheld on this connection).
Strings lifted out of the shipped bundle, so the claim above can be checked against them.