Bug Report: claude --continue broken after using claude --resume
Environment
- Version: Claude Code 2.0.24
- Platform: WSL2 Ubuntu 24.04.3 LTS (Noble Numbat)
- Node.js: v22.17.1
- Terminal: Windows Terminal
Issue Summary
claude --continue starts a new session instead of continuing the most recent conversation when that conversation was resumed using claude --resume (interactive selector).
Steps to Reproduce
- Start a Claude Code session:
claude
- Have a conversation, then exit
- Resume the session using interactive selector:
claude --resume (select from list)
- Continue the conversation for multiple messages
- Exit the session
- Try to continue:
claude --continue
Expected: Resume the session from step 3
Actual: Starts a completely new session with "Warmup" greeting
Root Cause Analysis
When a session is resumed via claude --resume interactive selector, it does NOT update ~/.claude/history.jsonl.
claude --continue relies on history.jsonl to find the "most recent conversation"
- Resumed sessions write to their session JSONL file (
~/.claude/projects/-<project>/<session-id>.jsonl)
- But they don't write entries to
history.jsonl
- Therefore
--continue cannot find them and starts a new session
Evidence:
- Session file:
~/.claude/projects/-home-diegocc/7fe87110-1039-456c-8009-9f5720ee0886.jsonl (300+ messages, 530KB)
- Last
history.jsonl entry for that session: timestamp 1761071167344
- Session continued for 2+ hours after that with no history updates
- After manually adding a history entry,
--continue worked correctly
Workaround
Manually append an entry to ~/.claude/history.jsonl:
echo '{"display":"Session resumed","pastedContents":{},"timestamp":'$(date +%s%3N)',"project":"'$(pwd)'"}' >> ~/.claude/history.jsonl
Expected Behavior
Resumed sessions should update history.jsonl for each user message, just like freshly started sessions do, so that --continue can find them.
Additional Notes
claude --resume interactive selector works correctly (no arrow key navigation issues)
claude --resume <session-id> returns "No conversation found" for active sessions (expected)
- Only the history tracking is broken
Impact
- Medium/High: Users cannot use
--continue after resuming sessions
- Workaround exists but requires manual intervention
Bug Report:
claude --continuebroken after usingclaude --resumeEnvironment
Issue Summary
claude --continuestarts a new session instead of continuing the most recent conversation when that conversation was resumed usingclaude --resume(interactive selector).Steps to Reproduce
claudeclaude --resume(select from list)claude --continueExpected: Resume the session from step 3
Actual: Starts a completely new session with "Warmup" greeting
Root Cause Analysis
When a session is resumed via
claude --resumeinteractive selector, it does NOT update~/.claude/history.jsonl.claude --continuerelies onhistory.jsonlto find the "most recent conversation"~/.claude/projects/-<project>/<session-id>.jsonl)history.jsonl--continuecannot find them and starts a new sessionEvidence:
~/.claude/projects/-home-diegocc/7fe87110-1039-456c-8009-9f5720ee0886.jsonl(300+ messages, 530KB)history.jsonlentry for that session: timestamp 1761071167344--continueworked correctlyWorkaround
Manually append an entry to
~/.claude/history.jsonl:Expected Behavior
Resumed sessions should update
history.jsonlfor each user message, just like freshly started sessions do, so that--continuecan find them.Additional Notes
claude --resumeinteractive selector works correctly (no arrow key navigation issues)claude --resume <session-id>returns "No conversation found" for active sessions (expected)Impact
--continueafter resuming sessions