Skip to content

[FEATURE]: show the provider and model id in message footers #53638

Open

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 by its display name only: ▣ Build · Claude Opus 4.5 · 29.0s. When the same model is reachable through more than one provider (openai and an OpenAI-compatible gateway clone, a direct API key and a proxy, two Anthropic accounts), every turn reads the same, and nothing on screen says which provider answered it. The prompt's model indicator shows the provider's display name, but that is the current selection, not the turn's, and two custom providers can share a display name too.

Proposal: a model_label setting in tui.json:

  • "name" (default): today's display names, unchanged.
  • "id": the providerID/modelID the turn actually ran on, e.g. anthropic/claude-opus-4-5 or openai-gateway/gpt-5.5, in every assistant message footer, and in the prompt's model indicator in place of the model and provider names.
// tui.json
{ "model_label": "id" }

Variant, duration and everything else on those lines stay as they are. The ID is the same string /models, --model and opencode.json's model use, so what the footer shows can be pasted straight into config.

Activity

  1. opencode-agent commented on Oct 7, 2026

    @opencode-agent
    Contributor

    Thanks for the detailed proposal. I checked this on v2.0.24, the latest release. After a turn with a model configured as simulation/gpt-sim-model, the footer reads Build · Simulated Model · 51ms. It shows only the model's display name, with no provider and no providerID/modelID. The TUI config also has no setting to change this. So the current behaviour is as you describe: two providers serving models with the same display name produce identical footers. I've recorded this as a feature request for the maintainers to consider.

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