{"version":"2.1.318","anchor":"clear-now-captures-tools-used-postmodelswitch-hooks-can-be","canonical_anchor":"clear-now-captures-tools-used-postmodelswitch-hooks-can-be","heading":"\/clear keeps a record of tools used, and model-switch hooks can wait to start","tier":"notice","area":"Slash Commands","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/clear-now-captures-tools-used-postmodelswitch-hooks-can-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### \/clear keeps a record of tools used, and model-switch hooks can wait to start\n\n\/clear now saves a record of the tools used and undoes it if the clear fails, and PostModelSwitch hooks can be held back\n\n**What**\n\n`\/clear` starts a new conversation with empty context. It now also saves a record of the tools that were used, and undoes that record if the clear fails.\n\nA hook is a command you set up to run when something happens in Claude Code. `PostModelSwitch` hooks run after the session's model changes. They used to start straight away. They can now be held until Claude Code says they may start. If the conversation has moved on in the meantime, or the hook never gets to start, Claude Code records that it was held.\n\n**Why**\n\nA model-switch hook should no longer fire after the conversation it belonged to has already changed, for example after a `\/clear`.\n\n- Area: Slash Commands\n- Names: `\/clear`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}