{"version":"2.1.275","anchor":"new-internal-event-kind-repl-mcp-needs-auth-added-to-synthet","canonical_anchor":"new-internal-event-kind-repl-mcp-needs-auth-added-to-synthet","heading":"New internal repl_mcp_needs_auth event kind added, but unused","tier":"soon","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/new-internal-event-kind-repl-mcp-needs-auth-added-to-synthet","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### New internal repl_mcp_needs_auth event kind added, but unused\n\nA new repl_mcp_needs_auth message kind exists internally but currently renders no content and nothing creates it\n\n**Unclear.** placeholder\n\n**What**\n\nA new event\/message kind called `repl_mcp_needs_auth` was added internally alongside existing kinds like `max_turns_reached` and `poll_events`. It appears in the enumerations\/state-key lists used for these message kinds, and in the renderer map that turns message kinds into visible content, `repl_mcp_needs_auth` is wired to a handler that always returns an empty array, meaning it produces no visible content.\n\n**Why**\n\nNothing in the current code actually constructs a message of this kind, so this has no visible effect yet. It looks like groundwork for a future feature (likely related to an MCP server, a way of connecting external tools, needing authentication) that has not been wired up to actually fire.\n\n- Area: MCP\n- Names: `repl_mcp_needs_auth`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}