[FEATURE] Timer showing how long you have left before cache expires.

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

If I have a long conversation, the difference between replying to Claude after 4 min 30 sec and replying after 5 min 15 sec is a significant portion of my weekly usage, given I'm on the pro plan, and sometimes I don't know whether I'm replying just in time or hacking a large chunk off my usage after reviewing code or drafting a long response.

Proposed Solution

It would be extremely convenient to have a timer showing how long until the cache expires. That way, I could send partial responses, request more time to review code, etc, resetting my TTL. Also, if my TTL has expired, I can know, so I can weigh the cost/benefit of continuing a long conversation vs. /clearing and starting a new one.

I don't mean to be alarmist, but I set the priority high based on the description of each category. In a pro plan with limited usage, triggering a full re-upload of a long conversation can drastically affect how much Claude I'm able to use on a given week, therefore satisfying the definition of a "significant impact on productivity."

Alternative Solutions

If a timer is too much, partial functionality could be provided through some indicator as to whether or not your TTL is still active or not. For instance, maybe change the color of the > symbol to red if the cache has expired. That would be better than trying to keep track of the system clock.

Priority

High - Significant impact on productivity

Feature Category

API and model interactions

Use Case Example

1: I and writing a response to Claude.
2: I worry that I might be approaching the end of my TTL.
3: I look at the timer.
4-a: I see I have plenty of time and continue composing.
4-b: I see I have nearly no time left, copy my whole response, delete it, then send Claude a brief response like "one sec"
4-c: I see I have missed my time, and, realizing the conversation was pretty long, I /clear and start a new one instead of triggering an expensive cache miss.

Additional Context

Mockup:

<img width="932" height="796" alt="Image" src="https://github.com/user-attachments/assets/fa1a4c6b-e67b-4b21-92f0-16855e679796" />