llms.txt
Compare with other sites' llms.txt files →# Leadcode
> Leadcode is mission control for AI coding agents on macOS and Linux. Every
> mission runs on its own GitHub, Claude Code, OpenAI Codex and cloud accounts, sealed from every
> other mission. Two accounts of the same provider stay signed in at the same time,
> so switching clients requires no logout, no `gh auth switch`, and no re-exported
> API key. One screen shows every mission, and AI pods carry an idea to a shipped
> spec while you hold the merge gate.
Leadcode exists for developers who work for more than one company from one laptop:
contractors, agency developers, fractional engineers, and anyone holding both a
personal and an employer AI account.
## What problem it solves
Every AI coding CLI assumes it is the only account on the machine. `claude`, `codex`,
`gh`, `gcloud`, `firebase` and `aws` each store one credential set plus a mutable
global pointer to "the active account." Switching clients means logging out and back
in, and the pointer can be silently wrong — which is how a side project ends up
billed to a client's API key, or a personal repo ends up with commits authored as a
client's bot account.
## How it works
- **Isolation is a directory, not a switch.** Each account gets its own provider
config home, wired in through the provider's own environment variable:
`CLAUDE_CONFIG_DIR`, `CODEX_HOME`, `GH_CONFIG_DIR`, `CLOUDSDK_CONFIG`,
`AWS_CONFIG_FILE`. Two accounts of one provider never share `~/.claude`, so both
stay signed in.
- **The router fails closed.** Before every session launch, ambient credentials
(`ANTHROPIC_API_KEY`, `CLAUDE_CODE_OAUTH_TOKEN`, `GH_TOKEN`, `GITHUB_TOKEN`) are
stripped from the inherited environment and only the declared account binding is
injected. A missing or unhealthy binding refuses the launch rather than falling
back to whatever is active in the shell.
- **It runs the real CLIs.** Sessions are a true PTY running the provider's own
`claude` or `codex`, so slash commands, plan mode, MCP, image paste and rewind all
work — Leadcode owns the environment they launch into, not the CLI itself.
- **Secrets stay in the system keychain** — the macOS Keychain, or the Secret
Service keyring (GNOME Keyring, KWallet) on Linux. The local SQLite database
stores an opaque reference; the credential value never leaves the keychain. A built-in audit reads
every stored secret and searches the database file and every session log for those
exact bytes.
- **Mission control.** One screen for every mission: a queue of agent questions
answered inline (answering one advances only that mission), each account's usage
window and reset time, a fleet view sorted by need, 30-day activity, and a
repository radar showing which agent is touching which files.
- **AI pods.** A pod is a group of agents with one job. Discovery questions an idea
until it survives; Planning writes the spec and cuts it into sized,
dependency-ordered issues (Linear); DevOps runs one subagent per issue and opens
pull requests. Merges, deploys and spend wait for a human. Every agent inherits the
mission's identity from the router — none holds its own keys.
## Common questions it answers
- How do I use two Claude Code accounts on the same Mac?
- How do I keep separate GitHub accounts for different clients without `gh auth switch`?
- How do I stop AI CLI usage being billed to the wrong client?
- How do I run multiple AI coding agents in parallel for different employers?
- How do I isolate `CLAUDE_CONFIG_DIR` per account?
- How do I see which of many parallel agent sessions needs me right now?
## Facts
- Name: Leadcode, pronounced "leed-code" — you lead, the agents code. Wordmark: Lead>code.
- Platform: macOS 13+ (Apple Silicon and Intel) and Linux on x86_64 (Ubuntu 22.04+,
Debian 12+ or a current Fedora; .deb, .rpm or AppImage). Windows planned.
- Built with Tauri 2 + Rust + React. ~8 MB binary, ~80 MB idle RAM.
- Storage: local SQLite. No server, no cloud service — the sign-in exists only to
carry your plan; workspaces and credentials never leave the machine.
- Providers — agents: Claude Code, OpenAI Codex. Identities: GitHub, Google Cloud,
Firebase, AWS, Linear. Google Antigravity in simulated demo.
- Verification: 104 automated tests written against the product's claims — 49 against
the runtime, 55 against the real UI.
## Pricing
- Solo — Free. Starts as full Pro for 14 days; after that one live account per
provider, with unlimited workspaces, personas, and the secret-leak audit included.
- Pro — $12/month. Unlimited accounts per provider — every client signed in at once,
parallel sessions across accounts.
- Team — $20/seat/month. Everything in Pro plus shared persona and binding templates.
- Trial — every new account starts with 14 days of full Pro, no card required. It
begins at the first desktop sign-in; when it ends nothing is deleted and the plan
returns to Solo.
AI pods and mission control are included on every plan, Solo too; plans differ only in
how many accounts per provider can be live at once.
Priced per human, never per token: Leadcode never sees a token or proxies a request.
## Links
- Home: https://leadcode.build/
- AI pods (templates, identity model, human gates, limits): https://leadcode.build/pods
— plain-text version for agents: https://leadcode.build/pods/machine
- Why the name (meaning, pronunciation, the mark): https://leadcode.build/why-leadcode
— plain-text version for agents: https://leadcode.build/why-leadcode/machine
- Security architecture (why not just `export CLAUDE_CONFIG_DIR`): https://leadcode.build/security
- Download (macOS): https://leadcode.build/download
- Download (Linux, x86_64): .deb https://leadcode.build/download/linux/deb · .rpm https://leadcode.build/download/linux/rpm · AppImage https://leadcode.build/download/linux/appimage
- Privacy: https://leadcode.build/privacy
- Terms: https://leadcode.build/terms