You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Agents panel: Separate OpenCode usage into its own collector instead of merging into Claude Code #7747
The Claude usage collector (omarchy-agent-usage-claude) currently scans OpenCode SQLite history (~/.local/share/opencode/opencode.db) and merges Anthropic-provider messages into Claude Code's local stats and "TOKENS BY MODEL" breakdown.
This causes confusion and data pollution in the Claude Code tab:
Model pollution: OpenCode internal, proxy, or experimental model identifiers (e.g. claude-sonnet-4-6, claude-opus-4-6, claude-sonnet-4-5) appear directly in the Claude Code "TOKENS BY MODEL" list.
Subscription mismatch: OpenCode sessions often use independent API keys, OpenCode Zen/Go credits, or third-party gateways rather than the Claude Code OAuth subscription. Merging them misrepresents the actual Claude Code usage and limits.
Expected Behavior
Claude Code collector (omarchy-agent-usage-claude) should only reflect Claude Code CLI native usage (~/.claude/projects/).
OpenCode usage should be tracked in its own dedicated collector / tab in the Agents panel (similar to the ongoing work in PR Add OpenCode Go collector for the Agents panel #7687 for OpenCode Go) so each tool's usage, models, and quotas remain accurate and isolated.
Steps to Reproduce
Use OpenCode with Anthropic provider models (recorded in ~/.local/share/opencode/opencode.db).
Use Claude Code separately.
Run omarchy-agent-usage-update (or let the agents widget refresh).
Open the Agents bar panel on the Claude Code tab.
Observe that "TOKENS BY MODEL" lists the model IDs and token counts aggregated from OpenCode.
Two additional open PRs implement the separate OpenCode Go provider requested here: #8065 and #8823. Both add an independent collector with local usage and rolling, weekly, and monthly limits; #8823 also adds dedicated panel assets and default-provider registration. Qualified link: these cover the separate-provider half of the report, but neither PR removes any legacy OpenCode scanning from another collector.
Activity
rookepoole commentedon Sep 1, 2026
Two additional open PRs implement the separate OpenCode Go provider requested here: #8065 and #8823. Both add an independent collector with local usage and rolling, weekly, and monthly limits; #8823 also adds dedicated panel assets and default-provider registration. Qualified link: these cover the separate-provider half of the report, but neither PR removes any legacy OpenCode scanning from another collector.