{"version":"2.1.315","anchor":"held-message-recognition-gated-by-a-killswitch-and-an-env-va","canonical_anchor":"held-message-recognition-gated-by-a-killswitch-and-an-env-va","heading":"Held-message recognition arrives with an opt-out variable","tier":"use","area":"Messaging","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/held-message-recognition-gated-by-a-killswitch-and-an-env-va","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Held-message recognition arrives with an opt-out variable\n\nA new held-message recognition feature can be turned off with `CLAUDE_CODE_DISABLE_HELD_MESSAGE_RECOGNITION`, which is also passed to remote sessions\n\n**Unclear.** It is not clear what held-message recognition does or when the internal check lets it run.\n\n**What**\n\nClaude Code has a new feature called held-message recognition, and a new environment variable (a named value set outside Claude Code) to turn it off, `CLAUDE_CODE_DISABLE_HELD_MESSAGE_RECOGNITION`. What the feature does is not described.\n\n- The feature is on only when an internal check passes, the variable is unset, and the remote kill switch `tengu_snappy_sunrise_killswitch` is not on. A further remote switch whose name was not resolved also gates it.\n\n- When the variable is set, the checks for the feature return false.\n\n- The variable is added to a list of known environment variables, and it is passed through to BYOC remote environments, taken either from your local environment or from `environment_variables`.\n\nNothing has been read about `tengu_snappy_sunrise_killswitch` yet.\n\n**Why**\n\nIf a change in how messages are handled causes trouble, setting this variable turns the feature off locally and in BYOC remote sessions, without waiting for a remote switch.\n\n- Area: Messaging\n- Names: `CLAUDE_CODE_DISABLE_HELD_MESSAGE_RECOGNITION`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}