Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.238 ·

MCP connect results are stamped with the account that started them

MCP connections that finish after you switch accounts get dropped, but almost all of it is dark.

Nothing to try yet In Development
JSON All of v2.1.238
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MCPArea: what it touches
In DevelopmentKind: in v2.1.238,
In DevelopmentSection of the release

Connect attempts are stamped with their account and discarded across a switch; only the policy-blocked path runs without the disabled discovery cache.

What

Every connect attempt is tagged with the account in effect when it began; results that settle after a switch are dropped and their sockets closed instead of being written into the app's server list. Also new: cached servers are re-dialled and adopted on lazy connect, and a disable or policy denial landing mid-flight replaces the row rather than losing to the connect. Only the policy-blocked path runs on a default build; the rest sits behind the discovery cache, which is off.

Details
  • An account change bumps a process-wide counter and fires a one-shot telemetry event.
  • Mid-flight denials produce a disabled row or a POLICY_BLOCKED failed row.
Evidence

applyConnectionResult: disposing connect that settled after a disable

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.238 →

Feedback