Preflight Checklist
What's Wrong?
Running /clear appears to execute successfully (no error, empty stdout), but the entire prior conversation remains fully accessible to the model in subsequent turns, and the terminal does not switch to the fresh-session view (no Claude logo screen reset, as normally happens after a successful /clear).
What Should Happen?
/clear should fully reset the session context, and the terminal should show a fresh session screen.
Error Messages/Logs
None — the command produced no error. It appeared as <local-command-caveat>/<command-name>clear</command-name> with empty stdout, indistinguishable from a normal successful run except for the context not actually being cleared.
Steps to Reproduce
- Run a normal working session with substantial conversation history.
- Run /clear.
- Observe that the previous conversation is still accessible to the model in the next turn, and the screen did not reset.
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
No response
Claude Code Version
2.1.207
Platform
Other
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
Observed 2026-07-06. Related to a second anomaly seen in the same session window — see linked /usage percentage issue (post both and cross-link with the resulting URLs).
Preflight Checklist
What's Wrong?
Running /clear appears to execute successfully (no error, empty stdout), but the entire prior conversation remains fully accessible to the model in subsequent turns, and the terminal does not switch to the fresh-session view (no Claude logo screen reset, as normally happens after a successful /clear).
What Should Happen?
/clear should fully reset the session context, and the terminal should show a fresh session screen.
Error Messages/Logs
Steps to Reproduce
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
No response
Claude Code Version
2.1.207
Platform
Other
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
Observed 2026-07-06. Related to a second anomaly seen in the same session window — see linked /usage percentage issue (post both and cross-link with the resulting URLs).