Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.246 Home All releases ←olderv2.1.245 v2.1.247newer→
Claude Code v2.1.246

MCP connections now report four auth-lifecycle moments to nobody

Not switched on
Useful1 Signal4
MCP Notable

MCP now fires auth-loss and reconnect events that nothing in this build listens to.

Four MCP auth-lifecycle events fire on lost auth, reconnect, cached-connection adoption and cached-dial failure, with no subscriber present.

What

MCP connection handling now fires events when authentication is lost mid-call, when a reconnect after re-authenticating reaches the connected state, when a cached connection is adopted, and when dialling a cached connection fails. Nothing in the build subscribes to any of them.

Details
  • The four are authLost, reauthReconnect, cachedAdopt and cachedDialFailed, none of which existed previously.
  • Every use of them in the build is a fire, never a listen, so they are instrumentation points waiting for a consumer.
Evidence

cachedDialFailed

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.246 →