Skip to content

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

Closed as duplicate

Description

@sagaciouszu

🐟

Summary

Feature request: add a CLI setting to show timestamps on messages in the TUI transcript. There is currently no cli.json field, keybind, or in-view toggle for this — messages show agent/model/duration footers but never a clock time, so a long session cannot be correlated with external events or logs.

Environment

  • opencode version: v2.2.6
  • OS: Linux 7.2.15-1-omarchy (linux x86_64)
  • Terminal: TERM=xterm-256color, COLORTERM=truecolor
  • Shell: /usr/bin/bash
  • Install/channel: latest (release)
  • Active plugins: none found in ~/.config/opencode/opencode.json

Reproduction

  1. Open any TUI session with user and assistant messages.
  2. Inspect the transcript for a clock time on any message.
  3. Search the CLI settings reference and the cli.json schema for a timestamp option.

Expected Behavior

A documented setting (e.g. session.timestamps: show | hide) that renders message times in the transcript, defaulting to the current behavior.

Actual Behavior

No option exists: https://opencode.ai/v2/cli.json contains zero timestamp matches, the CLI settings reference documents no such field in any group, and the keybind command list has no timestamp-related command. The transcript renders session.tps and mini.turn_summary metadata but no clock times.

Additional Context

Use case: matching transcript messages against external logs during long sessions. Verified against the V2 docs and published schema on 2026-11-10; not a V1-era feature being missed.

Activity

  1. opencodejr commented on Nov 10, 2026

    @opencodejr
    Contributor

    Thanks for the clear write-up, @sagaciouszu! I think this is a duplicate of #49742, which asks for the same thing: a v2 TUI option (e.g. session.timestamps with a /timestamps toggle, as in v1) that shows message times in the transcript.

    Possible duplicates and closely related issues, ordered by likelihood:

    The bot will close this issue as a duplicate in 1 day unless you reply explaining how your request differs from #49742. Feel free to add your use case (matching messages against external logs) there.

  2. neriousy commented on Nov 10, 2026

    @neriousy
    Member

    Thanks for the report. This is the same issue as #49742, so we're tracking it there. Closing as a duplicate. Please add any extra details on #49742.

  3. opencodejr commented on Nov 11, 2026

    @opencodejr
    Contributor

    Closing this as a duplicate of #49742, since there's been no reply in the past day saying how this request differs. That issue asks for the same v2 TUI option to show message timestamps (session.timestamps / /timestamps).

    If you'd like to follow it, please subscribe to #49742 or add your use case there (matching messages against external logs). #62530 is an open PR for a related opt-in timestamp setting. If your request is actually different, reply here and we can reopen it. Thanks, @sagaciouszu!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions