Repository navigation
[FEATURE]: Show timestamps on AI assistant messages in TUI #43243
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
The TUI shows timestamps on user messages (via the /timestamps toggle), but not on AI assistant responses. This makes it hard to see when the AI replied and how long operations took.
Add the AI response timestamp to the AssistantMessage footer, visible when the existing /timestamps toggle is enabled. The data is already available — message.time.created exists on all message objects. This is a small change to the AssistantMessage component in packages/tui/src/routes/session/index.tsx, reusing the existing Locale.todayTimeOrDateTime helper and the existing showTimestamps context.
No config changes needed — the toggle already exists, it just doesn't apply to assistant messages yet.
Reacted by Nikita Rudenko, sackosh, Prakash Dumbre and adamwmierzwiak
Activity
github-actions commentedon Aug 18, 2026
This issue might be a duplicate of existing issues. Please check:
/timestampsapplies to both user and assistant messages — same root ask.Please review those issues and consider adding a "+1" or linking your specific use-case there instead of opening a new issue.
AndyS77 commentedon Aug 18, 2026
Thanks for the references. Our PR (#43238) is intentionally narrow: it extends the existing
/timestampstoggle (which already works for user messages) to also showtime.createdin the assistant message footer. No new mode, no config changes, no data model changes — just makes the existing toggle apply consistently to both user and assistant messages.#29399 proposed a broader tri-state gutter mode — our PR doesn't conflict with that; it's a minimal fix for the gap today. #35348 asks for start/completion timestamps with ms precision — that's a separate, larger feature. #41589 is closed.
Happy to close this as a duplicate if maintainers prefer to track the assistant-timestamp gap under one of the existing issues. Otherwise this PR is ready for review.
test(tui): fix timestamp test assertions for locale-agnostic checks
Nowaker commentedon Oct 8, 2026
I built this for my own use on v1: #53195 adds
"turn_timing": { "time": true }totui.json(and/turn-times), which puts the completion time in every assistant footer. #53654 goes further with atimestampsoption that can also time tool calls, thinking and text blocks.v1 is maintenance-only, so these are there for anyone who wants them; a v2 version will follow.
opencodejr commentedon Oct 28, 2026
Thanks for the suggestion, @AndyS77!
The
/timestampstoggle, theshowTimestampscontext andLocale.todayTimeOrDateTimeyou mention are all from the OpenCode v1 TUI (versions 0.x/1.x, npm packageopencode-ai). v1 now only gets fixes for critical bugs such as data loss, security problems or crashes with no workaround, so a new feature for it is unlikely to be added.We'd recommend upgrading to v2 (
@opencode/cli, theopencodecommand). The v2 TUI is a separate implementation and works differently here:/timestampstoggle yet.If you'd still like wall-clock timestamps on assistant messages in v2, please reply here or open a new request that mentions you're on v2. And if you think this is critical for v1, let us know why.
opencodejr commentedon Oct 29, 2026
Closing this as not planned. Adding timestamps to assistant messages via the
/timestampstoggle is a feature request for the OpenCode v1 TUI, and v1 now only gets fixes for critical bugs. We didn't hear back that this also applies to v2.The v2 TUI (
@opencode/cli) already shows how long each response took in the assistant message footer. If you'd like wall-clock timestamps on assistant messages in v2, please open a new feature request and mention that you're on v2. Thanks again for the suggestion, @AndyS77!