Live token-throughput indicator for the OpenCode 2 TUI prompt composer.
While a session streams, the top right of the composer shows estimated observable tokens and throughput: ~1712 tok · ~51.5 t/s
When OpenCode reports terminal usage, the token count becomes exact while TPS remains approximate, for example 1715 tok · ~51.5 t/s. The result freezes until the next run starts. Nothing is shown on the home screen, or before the first observable output.
Built against the OpenCode 2 preview. The earliest known compatible beta is 0.0.0-beta-17595. The TUI plugin API is still moving, so a much newer or older build may drop the indicator without an error. If the figure never appears, check your version first, then open an issue.
Install it with the CLI's plugin command, which adds the entry to ~/.config/opencode/cli.json for you:
opencode2 plugin add opencode2-tpsOr add the package to ~/.config/opencode/cli.json yourself:
{
"plugins": ["opencode2-tps"]
}To set options, use the object form:
{
"plugins": [
{
"package": "opencode2-tps",
"options": { "display": "tps", "refreshHz": 12 }
}
]
}A running TUI picks up cli.json changes immediately. On first use it installs the package into its own cache under ~/.cache/opencode/npm/ on Linux — one millisecond-timestamped generation per spec, for example opencode2-tps@latest/<generation>/, with the newest generation winning.
The host reuses the newest installed generation without contacting the registry, so a restart alone may not pick up a new release. To upgrade, delete the spec's cache directory and restart:
rm -rf ~/.cache/opencode/npm/opencode2-tps@latestTo pin a version instead, put the range in the entry — "opencode2-tps@0.1.0". Every distinct entry gets its own cache directory.
The plugin ID is opencode2.tps. To switch it off without losing the entry and its options, add "-opencode2.tps" after it:
{
"plugins": [
{
"package": "opencode2-tps",
"options": { "display": "tps", "refreshHz": 12 }
},
"-opencode2.tps"
]
}The defaults are usable as they are. For the full option list, the ranges and more examples, see Configuration.
While output streams, the plugin estimates tokens from observable UTF-8 bytes at a default of 4.75 bytes per token and calculates a bounded rolling delivery rate. Complete text, reasoning, and tool-input events reconcile buffered or missed deltas without creating artificial live-rate spikes.
At the end of each model step, OpenCode's reported output and reasoning usage replaces the byte estimate. Settled TPS divides those exact tokens by observed step spans ending at session.step.streamed, the host's authoritative end of the model stream, published before local tools join. Hosts that do not publish the event fall back to the final model-content boundary. Either way, local tool execution and time between model calls are excluded.
OpenCode's built-in assistant-footer t/s divides visible output tokens by the same step spans, leaving hidden reasoning out of its numerator. This plugin counts output plus reasoning, so on reasoning models its settled figure reads higher than the built-in one — those tokens were generated too.
TPS is always approximate (~) because OpenCode does not expose token-level timestamps. Proprietary reasoning may be encrypted or represented only by a short summary, and some providers buffer tool arguments until completion. During those opaque intervals the live rate holds or becomes unavailable instead of continuously falling. Opaque provider state is never counted by byte length.
For more detail, see Architecture.
Every output event carries the ID of the session that produced it, so each session is measured on its own.
A sub-agent streams under its own child session ID. While it works, the orchestrator's number stops moving and holds the average of the output the orchestrator produced before delegating. Open the sub-agent's session to watch its live throughput.
To work on the plugin, see Development. To publish a new version, see Release.
MIT — see LICENSE.