[BUG] Conversation history shows "now" for old conversations, breaking sort order in VS Code extension

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?

Not duplicate as you close the 2 related one !

Description

In the Claude Code VS Code extension, the conversation history panel is unreliable. Many old conversations are timestamped as "now" (or "a few seconds ago") even though they are not recent. Because the list appears to be sorted by this timestamp, the ordering is wrong, and finding/resuming the actual most recent conversation becomes a frustrating guessing game.

Steps to reproduce

1. Use the Claude Code VS Code extension over several sessions across multiple days.
2. Open the conversation history panel.
3. Observe the timestamps and ordering of past conversations.

Expected behavior

• Each conversation shows its real last-activity timestamp.
• The history list is sorted by real last-activity time (most recent first).
• The most recently used conversation is easy to identify and resume.

Actual behavior

• Several old conversations are displayed with a now / "a few seconds ago" timestamp.
• The timestamp does not reflect the actual last activity of the conversation.
• As a result the sort order is wrong, and locating the genuinely latest conversation is difficult.

Environment

• Claude Code VS Code extension
• OS: Linux (WSL2 — Ubuntu on Windows)
• Editor: VS Code

Additional notes

The "now" value looks like it may come from a fallback/default when the real timestamp can't be read, rather than the conversation's actual last-modified time. If multiple conversations all fall back to "now", the sort key collapses and the list order becomes meaningless.

What Should Happen?

Each conversation shows its real last-activity timestamp (its actual last-modified time), not a fallback value.
The history list is sorted by that real timestamp, most recent first.
The most recently used conversation is reliably at the top, so resuming "the last one I worked on" is a single click — no guessing.

Error Messages/Logs

Steps to Reproduce

...

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.191 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

_No response_