[BUG] Opening a new session without --resume does not clear session history (and /clear doesn't actually clear)
Resolved 💬 5 comments Opened Aug 29, 2025 by ckapilla Closed Jan 5, 2026
Environment
- Platform (select one):
- [ ] Anthropic API
- [ ] AWS Bedrock
- [ ] Google Vertex AI
- [ X] Other: <!-- specify -->
- Claude CLI version: 1.0.96 (Claude Code)
- Operating System: Ubuntu 22.04
- Terminal: VS Code Terminal
Bug Description
<!-- A clear and concise description of the bug -->
Steps to Reproduce
- Start a session and exit.
- Start new session without --resume → fresh session (correct)
- Close session and VS Code
- Reopen VS Code, start new session without --resume → still fresh, no history (correct)
- Close that session, then start another session WITH --resume → unexpectedly restores the
original history from step 1
ALSO same thing happens after typing /clear and closing/restarting -- history is still present.
Expected Behavior
Based on what claude has told me, I expected the history to be permanently unavailable
Actual Behavior
as described in step 5 above.
Additional Context
I'm not saying this is behavior is a terrible thing, except when one has confidential information in the session history and would like to see it completely gone after a /clear. IN any event the behavior and the documentation are out of sync.
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗