{"version":"2.1.295","anchor":"idle-clear-hint-can-be-suppressed","canonical_anchor":"idle-clear-hint-can-be-suppressed","heading":"Idle sessions can offer a fresh conversation, and the idle \/clear hint can be hidden","tier":"notice","area":"Terminal UI","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/idle-clear-hint-can-be-suppressed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Idle sessions can offer a fresh conversation, and the idle \/clear hint can be hidden\n\nAfter a session sits idle, Claude Code can offer to start a new conversation with `\/clear`, and the idle \/clear hint can now be suppressed\n\n**What**\n\n`\/clear` starts a new conversation with empty context. Two changes affect how Claude Code suggests it after you have been away:\n\n- The prompt that offers a new conversation when you resume an old session now also has an idle trigger, for when the current session has been idle. It adds `evaluateIdleCacheQuota` and `askIdleCacheQuota`. For the idle trigger, `\/clear` is submitted as if from a key shortcut (`fromKeybinding`), in prompt input mode (`inputModeOverride` `prompt`), and keeping what is in the input box (`keepsComposer`).\n\n- The hint `new task? \/clear to save N tokens` can now be suppressed through `setHintSuppressed`. While suppressed, the hint is not scheduled, and any hint already shown is removed.\n\n**Why**\n\nAfter a long idle stretch the prompt cache (the stored copy of the conversation that makes the next request cheaper) may have gone stale, so Claude Code can offer a fresh start. Hiding the hint lets the interface avoid showing two suggestions at once.\n\n- Area: Terminal UI\n- Names: `\/clear`, `CLAUDE_CODE_IDLE_THRESHOLD_MINUTES`, `CLAUDE_CODE_IDLE_TOKEN_THRESHOLD`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}