Set up ashlr-plugin in Codex CLI and verify that its tools are available.
- Codex CLI with plugin support (
codex plugin --helplists the plugin commands) - Bun 1.3 or newer
Check Bun with bun --version. If it is missing, install it using the instructions at bun.sh.
From a shell, register the Ashlr marketplace, install the plugin, and confirm it is installed:
codex plugin marketplace add ashlrai/ashlr-plugin
codex plugin add ashlr@ashlr-marketplace
codex plugin listThe list should show ashlr. Restart Codex if it was already open. The plugin package includes the MCP server, Codex skills, and nudge-first hooks. The hooks provide tool guidance in context; they do not redirect or block Codex's native tools.
Run the packaging doctor from a terminal:
ashlr-plugin codex-doctor --jsonIf the ashlr-plugin command is not on PATH, run it from a clone of this repository:
bun run scripts/cli.ts codex-doctor --jsonTo list the tool names the plugin exposes without opening Codex:
ashlr-plugin toolsIn Codex, confirm the ashlr__ tools are listed, then try ashlr__savings or use ashlr__read on a project file. Ashlr tracks savings when Codex calls its MCP tools. Codex-native calls continue to work normally.
From a shell, read the local ledger as JSON:
ashlr-plugin stats --jsonFrom a clone: bun run scripts/cli.ts stats --json.
Or ask Codex to call ashlr__savings for a readable session and lifetime summary. The ledger is stored locally at ~/.ashlr/stats.json.
If you do not want to install the plugin package, add this to ~/.codex/config.toml and replace the path with the absolute path to your clone:
[mcp_servers.ashlr]
command = "bun"
args = ["run", "/abs/path/to/ashlr-plugin/scripts/ashlr-mcp.ts"]
env = { ASHLR_MCP_HOST = "codex-cli" }Restart Codex to load the server, then run codex mcp list to confirm ashlr is configured. When Codex starts the MCP server outside the project directory, pass cwd to Ashlr tool calls or set ASHLR_ALLOW_PROJECT_PATHS in this MCP server's environment to allow the project path. See multi-host MCP setup for details.
To preview the config changes a packaged install would make, run bun run scripts/cli.ts codex-install --dry-run --json from a clone.
The MCP tools and savings ledger work with Codex. Claude Code-specific features such as automatic tool redirects, the animated status line, slash commands, and OAuth bootstrap do not run in Codex. Codex users can check savings with ashlr-plugin stats --json or ashlr__savings.