Repository navigation
[FEATURE]: customizable status line with Go usage tracking #25875
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
Feature Request: Customizable Status Line
Claude Code supports a statusline setting in ~/.claude/settings.json that lets users display arbitrary info (git branch, time, costs, etc.) in the bottom bar.
It would be great if OpenCode had something similar — ideally a small DSL or template string in tui.json that renders into the status bar.
Specific use case: Go usage at a glance
As a Go subscriber, I'd love to see my usage for the current period directly in the TUI status line, e.g.:
Go: 42% (5h) | 38% (week) | 25% (month)
Right now I have to open opencode.ai/auth in a browser to check. Having this info persist in the terminal would save a lot of context switching.
What I'm imagining
// tui.json
{
"statusline": {
"left": "{git:branch} {go:usage_5h}",
"right": "{model} {go:usage_week} | {go:usage_month}"
}
}
Or even simpler — just expose the Go usage via an API/env that I could pipe into a plugin hook or a custom command.
Alternatives considered
- Using the plugin system — but there's no hook to modify the TUI chrome/status bar
- Using status_view (<leader>s) — useful but not persistent/glanceable
- Web console — works but breaks flow
Would love to hear if there's already a way to do this, or if this is something the team would consider adding.
**Labels:** `feature-request`, `tui`Reacted by Alex Arakelian, Adrien Taudiere, gui-bo, Yuri Alves and JDR
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon May 5, 2026
This issue might be a duplicate of existing issues. Please check:
These issues cover the two core components of this request — the customizable TUI status line and the Go usage data access.
kommander commentedon May 6, 2026
There is a plugin API that will be official soon that allows to do that as a TUI plugin. It's already in the production version, just not officially documented yet. If you point OpenCode at it should be able to figure it out and build a local local plugin that shows the info you need.
cioffiAI commentedon May 6, 2026
i'll give it a try
github-actions commentedon Jul 8, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.