{"version":"2.1.318","anchor":"connector-card-allow-tracking-behind-tengu-hazel-sluice","canonical_anchor":"connector-card-allow-tracking-behind-tengu-hazel-sluice","heading":"Session \"always allow\" choices for connector tools can be recorded","tier":"soon","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/connector-card-allow-tracking-behind-tengu-hazel-sluice","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Session \"always allow\" choices for connector tools can be recorded\n\nClaude Code can record a session-long \"always allow\" choice for an MCP connector tool, but only when a remotely controlled switch is on\n\n**Unclear.** It is not clear where these recorded choices are used, or whether they change what you are asked to approve.\n\n**What**\n\nClaude Code has new code that records a choice to always allow a particular MCP tool for the rest of a session. MCP tools are tools that come from connectors, which are outside services that plug into Claude Code. A session is one run of Claude Code from start to finish. The recording only happens when a remotely controlled switch reads \"on\". When the server sends nothing, the switch has no value.\n\n**Why**\n\nThis affects how long your permission choices for connector tools last within a session.\n\n- Flag `tengu_hazel_sluice`: Not enough to say (read for one account on one subscription tier against v2.1.318; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) 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: Permissions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}