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.221 Home All releases ←olderv2.1.220 v2.1.222newer→
Claude Code v2.1.221

Inline /mcp enable/disable detects changes made in another session

Use it now
Useful4 Signal0
MCP

When /mcp enable or disable does nothing, it now tells you if another session already changed it.

/mcp enable/mcp disable
What

When an inline /mcp enable or /mcp disable has nothing to do, it now tells you whether another session already changed that server's persisted state.

Details
  • distinguishes a genuine no-op from a state another session flipped underneath you
  • explains whether the server keeps working in the current session and whether it reconnects on next launch
  • names the sequence of commands that makes the change stick
Evidence

was re-enabled in another session, so this disable didn't persist

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

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.221 →