cd /news/developer-tools/leadcode-per-client-account-isolatio… · home topics developer-tools article
[ARTICLE · art-113695] src=leadcode.build ↗ pub= topic=developer-tools verified=true sentiment=· neutral

Leadcode – per-client account isolation for Claude Code, Codex, and gh

Leadcode, a new macOS app for agencies and contractors, provides per-client account isolation for Claude Code, Codex, and GitHub CLI, ensuring each client workspace uses its own GitHub, Claude, and API accounts with no mixing. The app, which starts with a 14-day full Pro trial, is priced per human rather than per token and is verified against gcloud 554.0.0, firebase-tools 15.22.4, and aws-cli 2.27.48.

read2 min views3 publishedAug 28, 2026
Leadcode – per-client account isolation for Claude Code, Codex, and gh
Image: source

Nothing mixed.

Each client gets a workspace signed in to their own GitHub, Claude, and API accounts — and your personal projects stay yours. Open a project: the right accounts are already there.

Three clients, three separate sets of accounts — all signed in, all running, none mixed.

One workspace per client, wired to their accounts. #

Sign in once per account. Each gets its own config home — CLAUDE_CONFIG_DIR, GH_CONFIG_DIR — so client work never touches your personal ~/.claude.

accounts/acc_northwind/claude-code

Navigate anywhere — nothing tears down. Questions from every workspace land in one inbox; answer inline, only that session advances.

The CLI you're already familiar with. #

A real PTY running the provider's own claude or codex — identity-injected, ambient-scrubbed, fail-closed. Every feature they ship works on day zero.

The agent cannot deploy to the wrong client. #

Bind a cloud account to a workspace and every session, every embedded terminal and every shell you open by hand is already that identity. No gcloud config configurations activate, no firebase login:use, no exported AWS_PROFILE to forget. Switching clients is opening a different window.

This is the part that stops being about convenience. An agent running terraform apply against the wrong project is not an inconvenience, it is an incident. Leadcode makes the identity structural rather than something you remembered to set.

Verified against gcloud 554.0.0 · firebase-tools 15.22.4 · aws-cli 2.27.48

Small, local, auditable. #

Priced per human, not per token. #

Every new account gets 14 days of full Pro — no card, it starts at your first sign-in. When it ends nothing is deleted; you go back to one live account per provider.

Starts as full Pro for 14 days. After that, one live account per provider — everything else stays the full app.

Download Unlimited accounts per provider — the reason Leadcode exists.

[Start free trial](#download)

For agencies and contractors who answer to more than one company.

[Talk to us](#download)

Sign in once per client. Then it just works. #

macOS 13+ · setup in about a minute · sign-in starts your 14-day Pro trial

── more in #developer-tools 4 stories · sorted by recency
── more on @leadcode 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/leadcode-per-client-…] indexed:0 read:2min 2026-08-28 ·