AIToday
Large Language ModelsAI Business & IndustryZenn AI/MLPublished: Oct 17, 2026, 10:00 JST

One human, 20+ Claude Code seats: AI師範's solo AI 'company'

One human, 20+ Claude Code seats: AI師範's solo AI 'company'

3 Key Points

  1. What happened

    AI師範, a salaried worker running a side business, runs 20+ Claude Code 'seats' (division-like roles) for everything from bidding on jobs to delivery. He published the seat-charter template and the first prompt he uses to launch each seat.

  2. Why it matters

    Splitting one Claude Code session into per-role seats kept work from bleeding between tasks and made it clear which seat handles a stalled job. His charter template spells out what each seat does not do, so seats stop straying into each other's work.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

The starting point for the experiment was a single Claude Code session asked to write applications, produce deliverables, and draft articles at the same time. According to AI師範, that arrangement produced three failures: a new task would pull in leftovers from the previous one, the growing context made each exchange costlier, and no one picked up a task that had stopped partway. The last problem is the one he calls the most troublesome, and he compares it directly to the everyday workplace question of who is going to take a job.

The fix was to copy corporate structure: divide the work into seats, each with its own charter. A delivery seat is created for each won order, which is why the number passes 20 in busy periods. The intended effect is that any one seat remembers less; the PR seat, for instance, does not know the contents of deliveries, by design.

AI師範 treats the 'what not to do' section as the important one. Without it, he says, a seat will helpfully reach into a neighboring seat's work—the PR seat starting to write applications, or the delivery seat starting to write articles. Handover is pushed into a file path rather than the conversation's memory. The next installment is set to cover how seats hand work to each other, starting with the case of the PR seat wanting to feature a delivery seat's case in an article.

FAQ
What is a 'seat' in this setup?
A seat is a role division, like a department in a normal company. AI師範 lists seats such as secretary, development, sales (bidding), delivery, PR, and IT support.
Why not just use one Claude Code session for everything?
He says three problems emerged: leftover context from earlier work bled into new tasks, longer conversations cost more per exchange, and nobody picked up stalled work.
What goes into a seat charter?
Four things: what the seat does, what it does not do, its quotas (what and how often), and which decisions it must ask the 'president' about versus handle on its own.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleClaude Opus 5.5 multi-agent tips: let managers delegate