Who it is forA developer who uses both Claude Code and Codex CLI and wants to see where each one's work went and what it cost.
The problemMixed history from two agents in one project list makes it hard to judge which agent handled which work.
The outcomeSeparate views of the same projects for Claude Code and for Codex, each with its own cost totals.
What you need first
- A Claude Code, OpenAI Codex CLI or Pi installation with existing session history on this machine
- Homebrew on macOS, or the install script on Linux or Windows, or Go installed
- A terminal to run bough in
Steps
- Install Bough as described in the README.
- Run
bough --agent=claudeto show only Claude Code work. - Run
bough --agent=codexto show only Codex CLI work. - Compare the totals for the same project in each view and note any figures that look wrong, as the README asks.
Prompt for your agent
In the bough repo at github.com/nickelsec/bough, run `bough --agent=claude --text` and `bough --agent=codex --text`. Report the total API-rate cost from each output and state which agent's figures the README says deserve more suspicion.
Caveat. The README says Codex and Pi support is newer and has had less exposure than Claude Code, so Codex figures deserve more checking.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for nickelsec/bough and "Compare agent costs between Claude Code and Codex"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer