Garcon

Garcon connects your coding tools to their providers. It assigns Codex conversations to accounts you choose and shows requests, usage, and errors in one place.

npm install -g ai-garcon@latest
garcon setup

Open localhost:4141. Add accounts under Providers, enable the Codex accounts you want in the pool, then copy your tool's connection settings. Installation help.

Your tools, your accounts

Codex uses enrolled Codex accounts only. Pi can use that pool or OpenRouter. Claude Code uses its selected Claude profile. Other compatible clients keep their configured provider.

New Codex conversations choose an eligible account by remaining quota relative to reset time. Existing conversations stay on their account. If it becomes unavailable, the request fails; Garcon doesn't silently switch providers or replay it elsewhere. Routing details.

Find the work behind a request

Sessions shows Codex task names, projects, routed accounts, and in-flight model requests. Search by title or ID, then drill into a session to see each model call, the tools it used, and its subagents. The ticker and request inspector show task names too.

Analytics shows tokens and estimated API-equivalent costs. Logs includes failures and interrupted streams. A separate usage widget shows subscription allowances and reset times.

Garcon records model traffic. A task with no request in flight might still be running tools or waiting for you.

Local by default

The dashboard and proxy share one Go process, with SQLite for local history. Prompts, replies, and OAuth tokens aren't saved in the ledger. Provider CLIs keep their logins; OpenRouter keys are stored separately. There is no cross-device sync.

These docs follow the current source. Your installed release may not yet include unmerged changes.