opentab

opencode keeps a tab. opentab opens it.

opentab-demo.mp4

A local, dependency-free terminal UI for your OpenCode spend. opentab reads OpenCode's own SQLite database and shows you exactly where your tokens and money went — by month, day, session, model, and subagent — including the recursive cost of every subagent a session spawned.

No backend. No telemetry. No accounts. Just curses + sqlite3 from the Python standard library. No pip install, ever.

Features

• Session cost breakdown
• Model attribution
• Recursive subagent costs
• Monthly and daily views
• Local-only
• Zero dependencies
• Demo mode for screenshots

Why this exists

OpenCode logs every session — cost, token breakdown, model, and the full parent/child subagent tree — into a plain SQLite file:

~/.local/share/opencode/opencode.db

That's the whole pitch: because it's a real database, you can query your own AI usage. opentab is what that looks like when you do.

Requirements

Python 3.9+ (standard library only — no pip install, ever) and a Unix-like OS with curses (macOS, Linux, WSL).

Install

One line (installs opentab into ~/.local/bin; re-run to update):

curl -fsSL https://raw.githubusercontent.com/hamidi-dev/opentab/main/install.sh | bash

Prefer not to pipe a script into your shell? opentab is a single self-contained file, so any of these work and are easy to audit first:

# clone (symlink install; `git pull` then auto-updates)
git clone https://github.com/hamidi-dev/opentab && cd opentab && ./install.sh

# or just drop the one file on your PATH
curl -fsSL https://raw.githubusercontent.com/hamidi-dev/opentab/main/opentab \
  -o ~/.local/bin/opentab && chmod +x ~/.local/bin/opentab

BIN_DIR=~/bin overrides the install target. A Homebrew tap (brew install hamidi-dev/tap/opentab) is planned once the first release is tagged.

Usage

opentab                          # open the browser, all time
opentab --days 30                # start within a window (change live with [ ])
opentab --since 2026-05-01 --until 2026-05-31
opentab --db /path/to/opencode.db  # default: ~/.local/share/opencode/opencode.db
opentab --demo                   # safe for live demos / screenshots (see below)

Demo mode

opentab --demo is for showing the tool to other people without leaking your real work. It never writes to the database — everything is transformed in memory on load:

• Session titles and project paths are replaced with deterministic, plausible fakes (stable across redraws).
• Sessions OpenCode recorded with no cost get a synthetic price derived from their real token counts, so there are no $0.00 / unpriced gaps on screen.

The shape of your data stays real — token counts, model mix, and already-priced costs are untouched. A DEMO — synthetic tag shows in the header so synthetic numbers are never mistaken for real ones.

opentab opens on a stacked Months / Days sidebar (lazygit-style). Tab flips focus between the two panels. Enter zooms the focused month's or day's detail full-screen (Overview / Models / Sessions, switch with h/l). On the Sessions tab, j/k pick a session and Enter opens that session's own detail — cost split, model mix, and subagent tree. Esc steps back out.

Keys

Key	Action
Tab	Flip focus between the Months and Days panels
Enter / +	Drill in: month/day zoom → (on Sessions tab) open a session
Esc / Shift-Tab	Step back out (session → zoom → browse)
j/k or arrows	Move in the current list / scroll detail
h/l	Switch detail tabs
g / G	Top / bottom
[ / ]	Narrow / widen the time range (7d … all time)
a	Show all time
s	Cycle sort for the session lists (cost / tokens / date / subagents / title)
/	Filter; x clears
r	Reload the database
?	Help; q quits

Windows

opentab uses Python's curses, which is Unix-only (not bundled with Windows Python). The supported way to run it on Windows is WSL — and that's the natural fit, since OpenCode on Windows usually runs inside WSL, so its database already lives in the WSL filesystem where opentab can read it.

If OpenCode's DB is somewhere non-standard, point opentab at it:

opentab --db /path/to/opencode.db

Native Windows (cmd/PowerShell) is not supported; it would need pip install windows-curses, which is untested here. opentab prints a short hint instead of crashing if curses is missing.

A note on cost accuracy

The numbers come straight from OpenCode's own data (cost/tokens per message, rolled up per session). They are local attribution of what OpenCode recorded. For providers with token-based or credit-based billing (e.g. GitHub Copilot), some sessions show tokens with a $0.00 local cost — those need account-level reconciliation against your provider, not this tool. opentab surfaces these as "unpriced tokens" so you know where attribution is incomplete.

Not affiliated

This project is not affiliated with or endorsed by GitHub, Microsoft, OpenCode, SST, or any provider. It only reads a local database you already have.

License

MIT — see LICENSE.