{"version":"2.1.295","anchor":"ctrlc-handling-gated-by-tengu-calm-riddle","canonical_anchor":"ctrlc-handling-gated-by-tengu-calm-riddle","heading":"Ctrl+C with nothing running is handled differently","tier":"soon","area":"Terminal UI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/ctrlc-handling-gated-by-tengu-calm-riddle","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Ctrl+C with nothing running is handled differently\n\nPressing Ctrl+C when no request is running no longer raises the stop-feedback notification, under a remotely controlled switch\n\n**Unclear.** It is not clear which setups the Cowork-related condition covers, so who sees this change is unknown.\n\n**What**\n\nWhen you press Ctrl+C while Claude Code is not working on a request, it no longer raises the notification that normally follows stopping a response. That press also now counts toward the double-press behaviour, where pressing Ctrl+C twice in a row takes a further action.\n\nThis new handling depends on a server-controlled switch, `tengu_calm_riddle`, combined with a check related to Cowork. The switch falls back to on when the server sends nothing.\n\n**Why**\n\nIt changes what Ctrl+C does, and what appears at the prompt, when nothing is running.\n\n- Flag `tengu_calm_riddle`: Not enough to say (read for one account on one subscription tier against v2.1.295; this account: no value returned, anonymous baseline: no value returned, compiled default: on) 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: Terminal UI\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}