Local-first MCP tools and dashboard for investigating Codex token usage, credits, costs, caching, and thread patterns.
2026-10-27
ดาว
196
เครื่องมือ
—
อัปไทม์
—
Codex Usage Tracker is a local usage-data product for answering questions about
how Codex work consumes tokens, time, tools, allowance, credits, and cost. It
turns local session metadata into exact, bounded facts and stable evidence that
an agent can explore and explain.
Current release and next direction
Version 0.28.0 is the current public release. Its six-tool MCP surface,
Evidence Console, and SQLite kernel remain supported while the replacement is
qualified.
The next product is a clean, agent-first kernel rather than a larger dashboard:
fast recent-history setup with explicit 24-hour through all-time coverage;
compact named queries and stable evidence selectors;
agent-owned interpretation instead of server-authored narrative findings;
installed Codex qualification measured for latency, MCP calls, response
bytes, model tokens, accuracy, and usefulness.
The 0.28 code remains a frozen oracle during the rewrite and is removed before
the clean replacement release. The new runtime does not migrate or open its
database.
The plugin launches the codex-usage-tracker executable from the pipx
environment. Start a fresh Codex task after installation so it discovers the
new plugin tool catalog.
Develop
python3 -m venv .venv
.venv/bin/python -m pip install -e ".[dev]"
just v
Use synthetic fixtures only. Do not commit or share real Codex logs, prompts,
responses, tool-output bodies, credentials, private paths, or local databases.
C
Codex Usage Tracker
douglasmonsky·196 ดาว·
Local-first MCP tools and dashboard for investigating Codex token usage, credits, costs, caching, and thread patterns.