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 ccusage opencode --helpnpx ccusage@latest opencode --helppnpm dlx ccusage opencode --helpBUN_BE_BUN=1 opencode x ccusage@latest opencode --helpopencode 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 located under OPENCODE_DATA_DIR (defaults to ~/.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~/.local/share/opencode/
└── storage/
├── message/{sessionID}/msg_{messageID}.json
└── session/{projectHash}/{sessionID}.jsonReport 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
Environment Variables
| Variable | Description |
|---|---|
OPENCODE_DATA_DIR | Override the root directory, or comma-separated root directories, containing OpenCode data |
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 ~/.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.