{"version":"2.1.281","anchor":"clear-now-tells-the-session-reset-what-triggered-it","canonical_anchor":"clear-now-tells-the-session-reset-what-triggered-it","heading":"\/clear now tells the session reset what triggered it","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/clear-now-tells-the-session-reset-what-triggered-it","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### \/clear now tells the session reset what triggered it\n\n\/clear now tells the session reset that it was the trigger and which command message started it\n\n**Unclear.** The finding does not say what the reset does with the trigger or the message ID.\n\n**What**\n\nWhen you run `\/clear` to start a new conversation, it now passes `resetTrigger: \"clear\"` and the ID of your `\/clear` message to the step that resets the session. It also still passes the title of the cleared conversation.\n\n**Why**\n\nThe reset now knows that `\/clear` caused it and which message asked for it.\n\n- Area: Sessions\n- Names: `\/clear`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}