{"version":"2.1.299","anchor":"plugin-input-refusal-gate-on-promptsubmit-and-commandr","canonical_anchor":"plugin-input-refusal-gate-on-promptsubmit-and-commandr","heading":"Plugins can't send prompts or commands into a session you just stopped","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/plugin-input-refusal-gate-on-promptsubmit-and-commandr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Plugins can't send prompts or commands into a session you just stopped\n\nPlugin calls that submit a prompt or run a command are refused if you stopped the session and haven't typed anything since\n\n**What**\n\nPlugins (add-on packages that extend Claude Code) can submit prompts with `$.prompt.submit` and run commands with `$.command.run`. Before, these calls were queued without any check. Now Claude Code checks first: if the session was stopped and nobody has sent input since, the call is refused.\n\n- `$.prompt.submit` still finishes, but reports a reason the prompt was dropped.\n\n- `$.command.run` fails with an error.\n\nThe check sits behind a remote setting that defaults to on when the server sends nothing.\n\n**Why**\n\nWhen you stop Claude Code, a plugin can no longer restart work behind your back. Plugin authors should handle the dropped-prompt reason and the error.\n\n- Flag `tengu_plugin_input_refusal`: Not enough to say (read for one account on one subscription tier against v2.1.299; 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: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}