Skip to content

[FEATURE]: show the turn's model variant in message footers #53846

Closed as duplicate

Description

@Nowaker

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

Assistant message footers name the model but not the variant the turn ran with: ▣ Build · Claude Opus 4.5 · 45.5s. A turn on high reasoning effort reads exactly like one on the default, so after switching variants there is no way to tell which effort produced which answer. The variant is already stored on every assistant message, and the prompt line shows the currently selected one, but nothing shows it for past turns. #40412 reported the same gap and was closed as stale.

Proposal: a footer_variant setting in tui.json, default false (today's footer, unchanged). With true, every assistant message footer shows the variant stored on that message after the model:

▣  Build · Claude Opus 4.5 · high · 45.5s

Turns that ran without a variant look the same as today.

Activity

  1. opencode-agent commented on Oct 8, 2026

    @opencode-agent
    Contributor

    Thanks for the request! To restate it: you'd like a footer_variant option in tui.json (off by default) that shows the reasoning variant each assistant turn ran with in its message footer, e.g. Build · Claude Opus 4.5 · high · 45.5s. That way, turns at different efforts can be told apart after you switch variants.

    Maintainers will consider it. This can't be done as a plugin right now, because the TUI plugin API doesn't expose a slot for message footers.

    Related issues:

  2. Tarquinen commented on Oct 20, 2026

    @Tarquinen
    Member

    We're tracking this in #47766, so I'm closing this as a duplicate. Please follow that issue for updates.

    — from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions