feat(tui): add configurable reply timestamps by NachiketKandari · Pull Request #62530 · anomalyco/opencode

NachiketKandari · 2026-11-07T07:52:29Z

Issue for this PR

Related to #53192

Type of change

Bug fix
New feature
Refactor / code improvement
Documentation

What does this PR do?

Adds optional wall-clock timestamps to assistant footers in the TUI.

v2 already shows the response duration and tokens/sec, but it has no equivalent of v1's /timestamps for assistant replies. This adds two opt-in cli.json settings:

session.timestamps (default false): show the reply's completion time and date.
session.date_format (default "locale"): locale, friendly (Nov 6, 2026), dd-mon-yyyy (06-Nov-2026), or iso (2026-11-06).

Both appear in Ctrl+P → Settings. The timestamp is based on message.time.completed, so it only appears after a reply finishes; a streaming reply does not show its start time as the completion time.

Build · Claude Sonnet · 15.8s · 42.3 tok/s · 9:41 PM · 06-Nov-2026

The formatter is in Locale.date. The feature is off by default, so existing configs are unchanged.

How did you verify your code works?

bun test test/config-v2.test.tsx test/util/locale.test.ts — 28 pass.
bun test --timeout 30000 test/app-lifecycle.test.tsx -t "keeps assistant footer metrics" — pass, including the rendered dd-mon-yyyy timestamp.
bun check on the changed files — no errors from this change.
bun run lint — no warnings or errors in the changed files.
Tests cover all four date formats and the default-off config.

Visual

<svg xmlns="http://www.w3.org/2000/svg" width="240" height="72" viewBox="0 0 240 72" fill="none">
  <style>
    text { font-family: ui-monospace, SFMono-Regular, Menlo, monospace; }
    .muted { font-size: 9px; fill: currentColor; opacity: .45; }
    .value { font-size: 9px; fill: currentColor; opacity: .9; }
  </style>
  <rect x="0.5" y="0.5" width="239" height="71" rx="6" stroke="currentColor" opacity=".18"/>
  <text x="12" y="22" class="muted">Build · Claude Sonnet · 15.8s · 42.3 tok/s</text>
  <text x="12" y="40" class="value" opacity="0">
    9:41 PM · 06-Nov-2026
    <animate attributeName="opacity" values="0;0;.9;.9;0" keyTimes="0;.2;.45;.8;1" dur="3s" repeatCount="indefinite"/>
  </text>
  <rect x="12" y="54" width="86" height="3" rx="1.5" fill="currentColor" opacity=".12"/>
  <rect x="12" y="54" height="3" rx="1.5" fill="currentColor" opacity=".4">
    <animate attributeName="width" values="12;86;12" dur="3s" repeatCount="indefinite"/>
  </rect>
</svg>

Screenshots / recordings

The terminal output is shown in the description above.

Notes

This is a feature I use daily. I have been running this patch locally on v2.2.5, and this PR contains only the feature, its tests, and the documentation change.

Checklist

I have tested my changes locally
I have not included unrelated changes in this PR

Added by the opencode bot (AI-generated).

Related: #49742, #53192, #62344

Public API: adds optional cli.json keys session.timestamps and session.date_format (backwards compatible)

opencodejr

The feature works as described. With session.timestamps on, I ran the TUI from source on base and on this branch with the simulated model. The footer changes from Build · Simulated Model · 66ms to Build · Simulated Model · 69ms · 7:54 AM · 07-Nov-2026. The related config, locale and footer tests pass, and the type check shows no new errors.

I couldn't get usable before/after screenshots from my run. Could you add before and after screenshots of the footer with the setting on?

Public API: adds two optional cli.json keys, session.timestamps (boolean, default false) and session.date_format (locale | friendly | dd-mon-yyyy | iso, default locale). Both also appear in Settings. This is backwards compatible: existing configs are unchanged and nothing is removed.

One concern, inline: the timestamp wraps in narrow terminals. Also worth knowing: #49742 asks for v1's per-message timestamps back, including on user messages and the /timestamps toggle, and has a design discussion with other contributors. This change only adds timestamps to assistant footers, so it covers part of that request.

Related: #49742, #53192, #62344

opencodejr · 2026-11-07T07:55:33Z

          <Show when={config.data.session.tps && tokensPerSecond()}>
            {(value) => <span style={{ fg: theme.text.muted }}> · {value().toFixed(1)} tok/s</span>}
          </Show>
+          <Show when={config.data.session.timestamps && timestamp()}>


The model name and duration on this line hide themselves below set terminal widths, but the timestamp doesn't. At 50 columns the footer wraps:

Build · Simulated Model · 51ms · 7:54 AM · 07-Nov-2026

Could it get a width check too, e.g. dropping the date first and then the time as the terminal gets narrower?

Fixed in 1168403. The width check now measures the footer parts, accounts for the scrollbar gutter, and drops the whole date first, then the whole time. tok/s is also hidden when the line no longer fits, and a resize regression test covers the exact column where the date drops. Screenshots are in the PR comment above.

Add session.timestamps to show the completion time and date in assistant footers, with session.date_format choosing locale, friendly (Nov 6, 2026), dd-mon-yyyy (06-Nov-2026), or ISO. The feature is off by default.

Account for the scrollbar gutter and hide tokens/sec when the footer line no longer fits, so the date and time drop as whole units instead of their last words wrapping.

NachiketKandari · 2026-11-08T06:24:14Z

Screenshots

Captured from the actual TUI renderer with session.timestamps: true and session.date_format: "dd-mon-yyyy".

Before — timestamps off

After — timestamps on

Narrow terminals

The timestamp now drops the whole date first, then the whole time, instead of letting the terminal wrap it:

Time only	Hidden

The width check also accounts for the scrollbar gutter, and hides tok/s when the footer line no longer fits, so the footer does not wrap at the boundary. A regression test covers the exact column where the date drops.

Scope note: this remains intentionally limited to assistant reply footers; per-message timestamps and the /timestamps toggle from #49742 are not part of this change.

opencodejr

My earlier concern is resolved: the footer no longer wraps in narrow terminals. I ran the branch from source with the simulated model at 120, 60, 50, 48 and 40 columns. The full timestamp shows when it fits. Narrower, the date drops and then the time, and the line stays on one row. The footer tests, including the new resize test, and the config and locale tests pass.

Public API: same as before. Adds the optional cli.json keys session.timestamps (boolean, default false) and session.date_format (locale | friendly | dd-mon-yyyy | iso, default locale). This is backwards compatible.

One behaviour change to be aware of: with tps on, tok/s now hides when it wouldn't fit, even if timestamps are off; before, it wrapped onto a new line. That seems reasonable. No other concerns.

Related: #49742, #53192, #62344

gvtret · 2026-11-11T15:57:52Z

+1 — this is the one v2 feature I miss daily.

Use case: long working sessions (often hours) in the TUI, where I need to correlate what the agent did with external events — server logs, CI runs, deploy times. The transcript currently tells me what happened and how long each turn took, but not when it happened. Post-hoc debugging today means exporting the session and scripting over time.created with jq, which is exactly what this PR removes.

The opt-in design looks right to me: session.timestamps off by default keeps the footer clean, and the four session.date_format options cover both human-readable and ISO needs (the ISO one is handy for pasting into tickets and logs). Also glad it lands in Ctrl+P → Settings, mirroring v1's /timestamps discoverability (#49742).

Would really appreciate seeing this merged. Happy to help test it on a long-running session if a review build is published.

opencodejr Bot reviewed Nov 7, 2026

View reviewed changes

NachiketKandari added 2 commits November 7, 2026 23:45

feat(tui): add configurable reply timestamps

0ea6345

Add session.timestamps to show the completion time and date in assistant footers, with session.date_format choosing locale, friendly (Nov 6, 2026), dd-mon-yyyy (06-Nov-2026), or ISO. The feature is off by default.

fix(tui): drop reply timestamp parts before they wrap

1168403

Account for the scrollbar gutter and hide tokens/sec when the footer line no longer fits, so the date and time drop as whole units instead of their last words wrapping.

NachiketKandari force-pushed the reply-timestamps branch from 2f99161 to 1168403 Compare November 8, 2026 06:22

opencodejr Bot reviewed Nov 8, 2026

View reviewed changes

benargio-pixel mentioned this pull request Nov 9, 2026

[FEATURE]: desktop: option to show message send timestamps in the session transcript #62857

Open

1 task done

opencodejr Bot mentioned this pull request Nov 10, 2026

tui: no setting for message timestamps in the transcript #63016

Closed

gvtret mentioned this pull request Nov 11, 2026

[FEATURE]: Show completion time and duration for every assistant turn in the TUI #53192

Open

1 task done

Lauri-Nomme mentioned this pull request Nov 12, 2026

Message timestamp option is missing in OpenCode CLI v2.0.8 #49742

Open

Navigation Menu

Repository navigation

feat(tui): add configurable reply timestamps - #62530

feat(tui): add configurable reply timestamps#62530
NachiketKandari wants to merge 2 commits into
anomalyco:devfrom
NachiketKandari:reply-timestamps

NachiketKandari commented Nov 7, 2026 •

edited by opencodejr Bot

Loading

Uh oh!

opencodejr Bot left a comment

Uh oh!

opencodejr Bot Nov 7, 2026

Uh oh!

NachiketKandari Nov 8, 2026

Uh oh!

NachiketKandari commented Nov 8, 2026

Uh oh!

opencodejr Bot left a comment

Uh oh!

gvtret commented Nov 11, 2026

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

NachiketKandari commented Nov 7, 2026 • edited by opencodejr Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Issue for this PR

Type of change

What does this PR do?

How did you verify your code works?

Visual

Screenshots / recordings

Notes

Checklist

Uh oh!

opencodejr Bot left a comment

Choose a reason for hiding this comment

Uh oh!

opencodejr Bot Nov 7, 2026

Choose a reason for hiding this comment

Uh oh!

NachiketKandari Nov 8, 2026

Choose a reason for hiding this comment

Uh oh!

NachiketKandari commented Nov 8, 2026

Screenshots

Narrow terminals

Uh oh!

opencodejr Bot left a comment

Choose a reason for hiding this comment

Uh oh!

gvtret commented Nov 11, 2026

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

NachiketKandari commented Nov 7, 2026 •

edited by opencodejr Bot

Loading