{"version":"2.1.311","anchor":"cloud-session-and-oauth-edge-changes","canonical_anchor":"cloud-session-and-oauth-edge-changes","heading":"Small changes to MCP sign-in, an error message and output styles","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/cloud-session-and-oauth-edge-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Small changes to MCP sign-in, an error message and output styles\n\nMCP servers using XAA sign-in no longer save discovery state, a dispatch error now lists `user` first, and an output style entry is added\n\n**What**\n\nSeveral small changes:\n\n- MCP servers (separate programs that give Claude extra tools) whose OAuth sign-in settings use XAA no longer have their discovery state saved.\n\n- An error message about dispatch tiers now lists `user` first: it reads \"(user, append, builtin, core)\" where it used to read \"(append, builtin, core)\".\n\n- A new entry, `explanatory-output-style`, is added to a feature list.\n\n- The reason Claude Code gave when auto mode was unavailable is no longer mapped.\n\n- The code around the `--forward-home-settings` error was reworked; the message itself is unchanged.\n\n**Why**\n\nEach change is small. Together they touch sign-in for MCP servers, dispatch tiers and output styles.\n\n- Flag `tengu_ccr_bridge`: Off by default, switched on for this account (read for one account on one subscription tier against v2.1.311; this account: on, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}