Leadcode – per-client account isolation for Claude Code, Codex, and gh
Isolates GitHub/Claude/Codex accounts per client so credentials never mix on one laptop
Leadcode gives each client (or your own projects) a persona with a separate config home for Claude Code, Codex, and gh — CLAUDE_CONFIG_DIR and GH_CONFIG_DIR are scoped per account, so opening a project auto-loads the right credentials instead of you running claude /logout and re-exporting ANTHROPIC_API_KEY by hand. The router scrubs ambient env vars (ANTHROPIC_API_KEY, GH_TOKEN, etc.) and fails closed — no binding means no launch, never a silent fallback to your shell — and can bind cloud identities like gcloud per workspace too. It runs a real PTY of the provider's own claude or codex CLI, so slash commands, plan mode, and MCP work day one, backed by 104 tests.
What holds up
- +Fails closed — no credential binding means no launch, never falls back to your shell
- +Scrubs ambient env vars like ANTHROPIC_API_KEY and GH_TOKEN before every session
- +Runs the real claude/codex CLI in a PTY — slash commands, plan mode, MCP all work day one
- +104 tests back the credential-isolation claims, not just a marketing promise
Mind the limits
- −macOS only — no Windows or Linux version
Featured here? Take the badge
Put it on your site — it links back to this review. Free for every listed product, always.
<a href="https://stillworks.dev/products/p/leadcode-per-client-account-isolation-for-claude-code-codex-/"><img src="https://stillworks.dev/badge/leadcode-per-client-account-isolation-for-claude-code-codex-.svg" alt="Picked by StillWorks" width="250" height="54"></a>