/resume isn't showing recent sessions with the latest update!

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Bug Report: Resume Picker Not Displaying Existing Sessions After v2.0.70 Update

Environment

• Claude Code Version: 2.0.70
• Installation Date: 2025-12-16 08:52
• Platform: Linux (WSL2)
• OS: Ubuntu on Windows (WSL)

Issue Summary

After updating to Claude Code v2.0.70 (released 2025-12-16), the claude --resume command no longer displays previously active conversation sessions in the interactive picker, despite these sessions being properly saved in the history file.

Steps to Reproduce

1. Update Claude Code to version 2.0.70
2. Have existing conversation sessions from before the update (sessions that were previously visible in resume picker)
3. Run claude --resume to open the interactive session picker
4. Observe that recent/important sessions are missing from the list

Expected Behavior

The --resume picker should display all conversation sessions that are saved in ~/.claude/history.jsonl, sorted by most recent activity, with session metadata (time elapsed, message count, git branch, initial message).

Actual Behavior

Recent conversation sessions (specifically those last active before the v2.0.70 update) do not appear in the resume picker, even though:

• Their data exists in ~/.claude/history.jsonl
• Their session directories exist in ~/.claude/session-env/
• They can still be resumed directly using claude --resume <session-id>

Evidence

Sessions Confirmed in History File

Investigation of ~/.claude/history.jsonl shows the missing sessions are properly logged with recent activity:

Session 1: bc0dbe45-7e62-4c9d-88b1-1bfc37758560

• Last activity: timestamp 1765879226084 (2025-12-16 ~10:33 AM)
• Multiple messages logged
• Project: /home/myName

Session 2: f3b29723-6228-41df-abef-d77782c6c38e

• Last activity: timestamp 1765479993051 (2025-12-11 ~09:26 AM)
• Multiple messages logged
• Project: /home/myName

Session Directories Exist

$ ls -lht ~/.claude/session-env/ | head -10
drwxr-xr-x 2 myName myName 4.0K Dec 16 11:25 5fafa962-ebf3-4fac-8dbe-1615c105a39d
drwxr-xr-x 2 myName myName 4.0K Dec  9 20:29 1965cf51-bce5-4aa5-8c29-af3593888cfb
drwxr-xr-x 2 myName myName 4.0K Dec  5 10:19 f3b29723-6228-41df-abef-d77782c6c38e
drwxr-xr-x 2 myName myName 4.0K Dec  2 07:59 bc0dbe45-7e62-4c9d-88b1-1bfc37758560

Both missing session directories exist with proper timestamps.

Direct Resume Still Works

$ claude --resume bc0dbe45-7e62-4c9d-88b1-1bfc37758560
# Successfully resumes the session

This confirms the session data is intact and the issue is specifically with the picker/display logic.

Hypothesis

The v2.0.70 update likely introduced a regression in:

• The session indexing logic used by the resume picker, OR
• The session metadata parsing/filtering logic, OR
• A change in the expected session data format that breaks compatibility with pre-update sessions

The bug appears to specifically affect sessions created before the update, while new sessions created after the update may display correctly.

Workaround

Users can still access their sessions by resuming directly with the session ID:

claude --resume <session-id>

Session IDs can be found by examining ~/.claude/history.jsonl.

Impact

• Severity: High - Users lose access to their conversation history through the normal UX
• Affected Users: All users who updated to v2.0.70 and have pre-existing sessions
• Data Loss: None - session data is intact, only the display mechanism is broken
• Business Impact: Severely impacts user experience, especially for users working on multiple long-running projects

Additional Notes

This issue was discovered by a user working on two important projects who noticed their most recent conversations vanished from the resume overview immediately after the update. The timing correlation (update installed Dec 16 08:52, issue noticed Dec 16 ~11:25) strongly suggests this is a regression introduced in v2.0.70.

Suggested Investigation Areas

1. Review changes to session picker/indexing logic in v2.0.70
2. Check for changes in history.jsonl parsing between v2.0.69 and v2.0.70
3. Verify session metadata requirements haven't changed in a breaking way
4. Test resume picker with pre-2.0.70 session data

---

Reported by: User via Claude Code interactive session
Date: 2025-12-16
Session ID: 5fafa962-ebf3-4fac-8dbe-1615c105a39d

---> PS Claude Code is not aware of it's own /feedback function!

What Should Happen?

Claude Code should show the latest sessions when asked: "/resume" but it doesn't it only shows older sessions

Error Messages/Logs

Steps to Reproduce

All the information you need is in teh report and is written by Claude Code itself to give all the required details.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

v2.0.70

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_