The client cockpit: one view for every project
The client cockpit is a simple idea: you operate every client project from one consistent place, and the tool keeps the projects apart so you do not have to hold them apart in your head. The principle is one lane per client, one view over all lanes.
Claude Code's June 2026 agents view makes the over-all view real. The claude agents screen shows every session you have running at once: which client job is working, which one is blocked waiting on a decision from you, and which one is finished. Instead of hunting through terminal tabs to remember what each client agent was doing, you read the board. That single screen is the cockpit's dashboard.
Set it up: one repo and one CLAUDE.md per client
The foundation of the cockpit is separation. Each client gets its own repository and its own CLAUDE.md, and that one rule prevents most of the mess before it starts.
- One repository per client: never share a working folder between two engagements. Separate repos mean separate histories, separate dependencies, and no chance of one client's code showing up in another's commit.
- One CLAUDE.md per client: this is the project memory that makes any agent productive in that client's codebase on day one. It holds their conventions, their stack, their do-not-touch list, and the context you would otherwise re-explain every session.
- Consistent structure across clients: keep the same folder shape and the same CLAUDE.md sections for every client, so switching lanes feels identical even though the contents differ.
The CLAUDE.md is the part that pays off most. A good one means you open a client's project and the agent already knows the rules, so you spend your time on the work instead of the briefing. Our guide on [CLAUDE.md templates by project type](/blog/claude-md-templates-by-project-type) gives you a starting shape for each kind of client.
Run cross-client tasks in a single session
Some jobs are the same across every client, and doing them one repo at a time is wasted effort. The June 2026 multi-repository sessions let a single Claude Code session operate across several local repositories at once, which is exactly what an agency needs for the work that repeats.
- A security patch: bump the same vulnerable dependency across every client that uses it, in one pass, instead of opening each project in turn.
- A shared convention change: roll out the same lint rule or the same CLAUDE.md section to all of your active clients at once.
- A portfolio audit: ask one session to check every client repo for the same issue and report which ones are affected.
The leverage here is real: the work that used to scale with your client count now happens once. That is how you take on the eighth client without it feeling like eight times the maintenance.
Keep client work from bleeding together
The power to touch every client at once is also the risk. The one discipline that makes the cockpit safe is strict separation of anything sensitive, and this is not optional when other people's businesses are in your care.
- Never share keys: each client's API keys, tokens, and credentials live only in that client's project, in its own environment file, never in a shared location. One client's key should never be reachable from another client's session.
- Never share data: do not let one client's data, customer records, or content land in another client's repo, prompt, or context. A multi-repo session is convenient, but you still decide what goes where.
- Scope each task: when you run a cross-client job, name the repos it should touch and confirm the agents view shows it acting only on those. Do not let a broad instruction wander into a project it had no business in.
A Monday operating routine
Here is a routine that turns the cockpit into a habit. It takes about fifteen minutes and sets the week up so no client quietly falls through the cracks.
- Open the agents view and read the board: what finished over the weekend, what is still blocked, and on what.
- Clear every blocked job first, because a blocked agent is a client waiting on you.
- Run your one cross-client pass for the week: the shared dependency check or convention update, done once across all repos.
- Glance at each client's CLAUDE.md and update anything that drifted, so the project memory stays true.
- Queue the week's work per client, then let the cockpit show you status instead of you chasing it.
Done weekly, this is what lets a small team carry a full client roster calmly. The point of the cockpit is not to do more frantic switching faster, it is to switch less and see more. Once your delivery runs this way, turning it into a repeatable offer is the natural next move, which our guide on [how to productize a service with Claude Code](/blog/how-to-productize-a-service-with-claude-code) walks through.
Run your agency with us
Inside Claude Code Club we help agency owners build the systems that let them carry more clients without more chaos: the per-client CLAUDE.md playbooks, the cross-client routines, and the offers that turn it all into revenue. Start with the [curriculum](/curriculum) or join us at https://www.skool.com/claudecodeclub/about and bring the client workload you most want to get under control.
Frequently asked questions
How do I run multiple client projects in Claude Code without mixing them up?
Give each client its own repository and its own CLAUDE.md so context, code, and credentials stay separated. Use the agents view to see every running job on one screen, and when you run a cross-client task, name the exact repos it should touch. The separation is what keeps one client's work from leaking into another's.
Can one Claude Code session work across several repositories?
Yes. The June 2026 update added multi-repository sessions, so a single session can operate across more than one local repository at once. That makes cross-client jobs like a synchronized dependency bump, a shared convention change, or a portfolio-wide audit possible from one place instead of one project at a time.
What is the client cockpit method?
It is operating every client project from one consistent command center: one repository and one CLAUDE.md per client for separation, the agents view as your dashboard over all running jobs, and multi-repo sessions for the work that repeats across clients. The goal is to switch lanes less and see the whole roster at a glance.
How do I keep client data and keys separate across projects?
Keep every client's API keys and credentials only in that client's project and environment file, never in a shared location. Never let one client's data land in another client's repo or prompt. When running a cross-client task, scope it to named repositories and confirm in the agents view that it touched only those. Treat each client boundary as a hard wall.
Last reviewed by Duncan Rogoff on June 30, 2026
