Model has no awareness of elapsed time between messages - feedback from a delivery driver using Claude Code for a year

I'm a Coupang delivery driver in Korea. I work 17-hour days and get one day off
every 23 days. For over a year I've been building a personal crypto trading system with
Claude Code, sitting down at the computer for a short while every 2-3 days.

## The problem

**The model has no idea how much time has passed between messages.**

Over a five-day span (Sep 5-9) it referred to the entire conversation as "today" and
"just now". It even wrote a *future* timestamp (23:55) into a log file while the actual
time was 23:10. Every single time I have to correct it: "what time is it now", "that was
days ago, not a moment ago".

## Why this matters for ordinary users

The whole reason people keep multiple chat windows open is that each session holds
different context. But if the model can't track time even *within* one session, the user
has to remember and restate the entire chronology themselves.

I'm not a developer. I check in for a few minutes every 2-3 days, often late at night
after work, sometimes after a drink. **I don't remember when I said what.** Assuming the
user will carry that memory is assuming everyone is as sharp as the model is. Most of us
aren't. That's exactly why we come back to the same chat - we expect *it* to remember.

This is a UX/UI problem as much as a model one.

## Proposal

Include a timestamp and an elapsed-time delta with each user message, and surface it in
the interface. For example:

```
[2026-09-09 23:20 KST - 2 days since your last message]
```

## My current workaround

I had the assistant write a `UserPromptSubmit` hook that injects the current time and the
gap since the previous message:

```
[TIME] 2026-09-09 23:20 KST (Wed) - 19 seconds since last message
```

It works. It even warns when the gap is over 6 hours ("check what happened in between")
or over 12 hours ("don't lump this together as 'today'").

But **most users will never write a hook.** I only managed it because the assistant wrote
it for me. This should be built in.

Thanks for reading. Writing this on my day off.

The issue names no implementation files or tests. Start by examining the UserPromptSubmit hook workaround and how Claude Code represents and surfaces user messages; done means each user message includes an accurate timestamp and elapsed-time delta in the model context and interface.

Vom Indexierungsmodell aus dem Issue-Text verfasst.