About codex-usage-dashboard
codex-usage-dashboard is a skill for launching a Codex usage dashboard. It verifies and, when needed, installs the matching native runtime before starting or reusing a local service; it also supports headless launch, stopping, and snapshot export.
Key features
- 01Verifies and installs the matching runtime
- 02Starts or reuses the local Rust service
- 03Opens the local dashboard page
- 04Supports headless launch and explicit stop
- 05Exports a local-device snapshot
Use cases
- 01Launch the Codex usage dashboard
- 02Start the service without opening a browser
- 03Stop the running service
- 04Export a local-device snapshot
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ luyh7/ codex-usage-dashboard --skill codex-usage-dashboardAfter installing, type/codex-usage-dashboardin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
native.jsonagents/openai.yamlscripts/install_runtime.mjsDetails
From the project READMEResolve paths relative to this SKILL.md, regardless of the user's project directory.
- From this skill directory, run
node scripts/install_runtime.mjs --ensure. This verifies the installed binary againstnative.jsonand its manifest, downloading the matching release when missing, outdated or still using the classic interface. Run this check after skill updates too; an existing executable alone does not prove it matches the skill. Node 18+ is required for this check; a download also requires internet access. On failure, report the installer error and the source-build instructions in the repository README; do not launch an old runtime or claim the dashboard started. - Run the verified native executable printed by the check:
runtime/codex-usage-dashboardon Linux/macOS, orruntime/codex-usage-dashboard.exeon Windows. Its default action starts or reuses the Rust service on port 8765 and opens the dashboard athttp://127.0.0.1:8765/. - Return the URL printed by the successful launcher. If browser opening is unavailable, give the user that link. An occupied, unmanaged port is an error; leave its process running and report the launcher's explanation.
Use --no-browser for a requested headless launch, --stop for an explicit stop,
and --export-snapshot PATH for a requested local-device snapshot export. Paths
containing spaces must remain one argument. Direct native launches require no
Python, Node or Rust toolchain.