{"version":"2.1.318","anchor":"clear-ends-the-main-thread-conversation-and-ask-open-at-id","canonical_anchor":"clear-ends-the-main-thread-conversation-and-ask-open-at-id","heading":"\/clear formally ends the conversation, and commands can run while a question waits","tier":"notice","area":"Slash Commands","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/clear-ends-the-main-thread-conversation-and-ask-open-at-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### `\/clear` formally ends the conversation, and commands can run while a question waits\n\n`\/clear` now ends the main conversation, some commands can run while a question is open at idle, and SDK-sent messages carry an empty blocked-tool list\n\n**Unclear.** It is not clear what the built-in check tests, so it is unknown who gets the `\/clear` and open-question changes.\n\n**What**\n\nWhen a check built into Claude Code passes, two things change:\n\n- `\/clear` now formally ends the main conversation and records that the conversation was cleared.\n\n- When Claude has a question open for you and is otherwise idle, commands meant to run immediately can now run.\n\nSeparately, messages sent in through the SDK, the toolkit for driving Claude Code from your own programs, now carry an empty `disallowedTools` list, the list of tools Claude is not allowed to use.\n\n**Why**\n\nThis points to new handling for typing while a question is waiting.\n\n- Area: Slash Commands\n- Names: `\/clear`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}