OpenCode Data Source (Beta)

OpenCode support is experimental. Expect breaking changes while both ccusage and OpenCode continue to evolve.

ccusage can read OpenCode session logs as one of its supported local data sources. OpenCode is a terminal-based AI coding assistant that supports multiple AI providers.

Focused Views

bunx (Recommended)

bunx ccusage opencode --help

npx

npx ccusage@latest opencode --help

pnpm

pnpm dlx ccusage opencode --help

opencode x

BUN_BE_BUN=1 opencode x ccusage@latest opencode --help

opencode x option

The opencode x option requires the native version of OpenCode. If you installed OpenCode via npm, use the bunx or npx options instead.

Data Source

The CLI reads OpenCode message and session JSON files from OPENCODE_DATA_DIR when it is set. Otherwise, it uses ${XDG_DATA_HOME:-$HOME/.local/share}/opencode. OPENCODE_DATA_DIR can be one directory or a comma-separated list of directories.

OPENCODE_DATA_DIR="$HOME/.local/share/opencode,/backup/opencode" ccusage opencode daily

${XDG_DATA_HOME:-$HOME/.local/share}/opencode/
└── storage/
    ├── message/{sessionID}/msg_{messageID}.json
    └── session/{projectHash}/{sessionID}.json

Report Views

Focused view	Description	See also
ccusage opencode daily	Aggregate usage by date (YYYY-MM-DD)	Daily Usage
ccusage opencode weekly	Aggregate usage by ISO week (YYYY-Www)	Weekly Usage
ccusage opencode monthly	Aggregate usage by month (YYYY-MM)	Monthly Usage
ccusage opencode session	Per-session breakdown with parent/subagent hierarchy	Session Usage

These views support --json for structured output and --compact for narrow terminals. See the linked ccusage documentation for detailed flag descriptions.

Session Hierarchy

OpenCode supports subagent sessions. The session report displays:

• Bold titles for parent sessions with subagents
• Indented rows (↳) for subagent sessions
• Subtotal rows combining parent + subagents

Forked Sessions

When OpenCode v2 forks a session, it copies the parent's history into the fork. ccusage counts only the usage the fork generates itself, so copied turns are not counted twice in session, daily, weekly, or monthly reports. If the fork's parent session or boundary message is no longer in the database, the fork keeps all of its rows.

Claude Agent Provider

The claude-agent provider runs Claude Code under the hood, so each turn is also saved in Claude Code's own logs. In unified reports such as ccusage daily, ccusage skips the OpenCode copy of turns the Claude source already counts, so they are priced from the Claude Code logs. OpenCode stores only a model alias such as opus, while Claude Code records the exact model, so its costs are accurate.

ccusage matches OpenCode rows to Claude usage by Claude Code session, not by individual turn:

• Daily, weekly, and monthly reports skip an OpenCode claude-agent row when the Claude source counted usage from the same Claude Code session on the row's date, in the Claude source's timezone. Rows still count when the Claude Code log is gone, holds no usage for that day, holds only subagent usage, or falls outside the Claude source's date range.
• Session reports match whole Claude Code sessions, because a Claude session row holds all of its usage, including days outside the Claude source's date range. Resumed and forked transcripts repeat earlier turns, and ccusage keeps one copy of each repeated turn. The OpenCode rows of a session whose own main-thread turns survive are skipped when every transcript holding them is included. The rows of a session whose turns all survive under other sessions are skipped only when every transcript holding those copies is included. When all transcripts are included, which one keeps a repeated turn does not affect the total. When the Claude window includes only some of them, a repeated turn can be left out, if a session's rows are skipped while its kept copy is in an excluded transcript, or counted twice, if the turns that decide whether a session's rows are skipped (its own surviving main-thread turns, or its kept copies when it has none) span included and excluded transcripts, since its rows are then kept.

Because OpenCode dates a turn by when it started and Claude Code dates each model call, a turn that runs across midnight can be off in the daily family. It is counted twice when Claude has no usage from that session on the day the turn started. With --until on that day, the calls Claude logs after midnight are left out, even though OpenCode dates the whole turn on the earlier day. ccusage opencode always shows every claude-agent row.

Environment Variables

Variable	Description
OPENCODE_DATA_DIR	Override the root directory, or comma-separated root directories, containing OpenCode data
XDG_DATA_HOME	Base directory for OpenCode data when OPENCODE_DATA_DIR is not set
LOG_LEVEL	Adjust verbosity (0 silent ... 5 trace)

Cost Calculation

OpenCode stores cost: 0 in message files. Costs are calculated from token counts using LiteLLM pricing. Model aliases (e.g., gemini-3-pro-high → gemini-3-pro-preview) are handled automatically.

Troubleshooting

No OpenCode usage data found

Ensure the data directory exists at ${XDG_DATA_HOME:-$HOME/.local/share}/opencode/storage/message/. Set OPENCODE_DATA_DIR for custom paths or comma-separated archive roots.

Costs showing as $0.00

If a model is not in LiteLLM's database, the cost will be $0.00. Open an issue to request alias support.