[FEATURE] Given option to add the current date and time for each claude code reply

Resolved 💬 3 comments Opened Nov 29, 2025 by DennisPeriquet Closed Dec 3, 2025

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

When using claude code, I often use the /resume function to resume a previous session. It works fine but when I see the context, I'd like to know when I interacted with claude. This is useful because if it's quite recent, I know it's relevant, but if it's from months ago, I probably don't care as much about this session and probably mistakenly resumed the wrong session.

Proposed Solution

Add an option in to allow timestamps for replies.

Here's an example (I also added some "=" signs to help my eyes target the start of the reply):

> take a look at this PR and see if you can get its labels and if it needs a rebase https://github.com/openshift/release/pull/67862 

⏺ ==========2025-11-29 10:29:30=============

  I'll check that GitHub PR for you, Dennis. Let me use the GitHub CLI to get the PR information including labels and rebase status.

Alternative Solutions

For now, I've done this in my ~/.claude/CLAUDE.md:

# Communication Style
  - At the start of a reply use "==========<current date and time>=============" so I can easily find the begining of your reply and track when it happened.

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

I'm working on some code in a claude code session in project A. I make a lot of progress.

I open up another instance of claude code in project B.

I open up another claude code in project A I make more progress.

I have multiple terminals up.

I come back to the first instance of claude code and see that my last interaction was some weeks back but I know I did a lot of work in the past several days. This alerts me that my session is old and I probably need to find the other claude instance where I worked on the project more recently or quit that session and resume a more recent session. If I just resume the old session, all that context could be out of date as things will most likely have changed.

Additional Context

For people that have a lot of terminals up and sometimes several claude code sessions, this would help them understand what is stale (most likely no longer relevant) or recent (relevant).

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗