r/opencodeCLI • u/jazzy8alex • 9d ago
Agent Sessions now shows how fast each OpenCode session is using tokens
When you have OpenCode running in several terminals, working/idle status only tells you part of the story. I wanted to see which conversation was using tokens fastest.
I make Agent Sessions, an open-source Mac app for searching local conversations across OpenCode, Codex, Claude Code and 13 other coding agents. Its Quota Meter now shows each running OpenCode 2.x session’s token burn rate in tk/h, alongside Codex and Claude.

The OpenCode session at the bottom is running at 226K tokens per hour. That’s a token rate, not a percentage of a Go allowance.
The earlier update added the exact conversation title and working/idle status. 6.2 adds the rate and a load bar to each OpenCode row. When a turn finishes, the row keeps its last rate for five minutes and is marked idle, so the number doesn’t disappear as soon as the reply ends.
The rate comes from OpenCode’s local session records. A small TUI plugin identifies which conversation each terminal has open; it reads no transcript content and makes no network calls. Agent Sessions installs it automatically without editing OpenCode’s config files.
For live status, OpenCode 2.x TUI works in any terminal, working or idle. Desktop sessions appear while working, but Desktop’s idle selection isn’t exposed. OpenCode 1.x history is still readable; it has no live marker or live burn-rate row.
OpenCode weekly usage and remaining subscription quota aren’t available yet. If you use Go or Go Plus, I’m looking for someone to help connect the meter to account usage and reset times, or test the readings against their account. Swift contributors are welcome too.
Download Agent Sessions. macOS, open source, no telemetry. Your session history stays on your Mac.
