[FEATURE] Desktop Code tab: date dividers and per-message timestamps in the conversation transcript

Status Open
Maintainer reply None cached
Activity 0 comments · opened Oct 15, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

In the Claude desktop app (Code tab) the conversation transcript shows no dates and no times.

I run many long sessions that continue over several days, and the sidebar holds dozens of sessions across projects. When I scroll back in a session I cannot tell on which day, or at what time, a prompt or a reply was written. I cannot see where one day ends and the next begins, I cannot match a message to something I did at a known time (for example a server upload), and I cannot see how long a task took.

Proposed Solution

  1. A date divider in the transcript before the first message of each calendar day, in the user's locale and time zone (for example "Thursday, 15 October 2026").
  2. A time label on every user prompt and every assistant reply (for example "15:51"), in local time. Visible at all times would be best; on hover at least.

Alternative Solutions

There is no setting for this in the app. As a workaround I ask Claude to mark a chapter with the date at the start of each day (mark_chapter), but this depends on the model remembering to do it, and it gives no time for individual messages.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

  1. A session starts on 11 October and I continue it on 15 October.
  2. I scroll up to find what I asked on 11 October in the afternoon.
  3. All messages look the same: no day boundary, no times. I have to read everything to find the place.
  4. With date dividers and times I would jump to the right place at once.

Additional Context

Platform: Windows 11, Claude desktop app, Code tab. Related but different: #102246 (last-activity time in the Recents list).

View original on GitHub ↗