kingshand

One Claude Code session you talk to, which puts every other one to work. kingshand takes a description of the work, writes a brief, waits for your approval, and runs each worker as its own Claude Code session in its own git worktree. Windows, PowerShell 7, MIT licensed.

Install it · Read the design decisions · Source on GitHub

The problem it solves

Running one Claude Code session is easy. The trouble starts at three: a fix in one repository, an investigation in another, a flaky test somebody has to sit with. You become a tab-juggler - three terminals, three sets of context in your head, and no way of knowing which session went quiet an hour ago because it is waiting on a question nobody is there to answer.

kingshand makes one session the only one you talk to. It dispatches the others, watches their screens rather than a status word, and comes back to you when there is something to decide.

What it gives you

• Parallel workers. One background session per unit of work, each isolated in its own git worktree, so several tickets can be in flight without treading on each other.
• Two gates. You approve what is dispatched and you approve what lands. Both can be turned off per project.
• A delivery posture per project. A repository is registered local-only, direct-PR or no-mistakes. Nothing is dispatched into a repository that is not registered, and the posture is read rather than guessed at.
• A queue that survives a restart. Work items, dependencies and held decisions are stored on disk, because a decision that lives only in the conversation is a decision you will lose.
• A digest at session start. Registered projects, live workers, the queue, your standing instructions and the curated memory, all handed over when the session opens, so a restart is close to a non-event.
• Short replies, and a review surface for what cannot be short. Next action first, numbered steps, no preamble. Anything you have to decide opens in your browser instead of scrolling past in chat.
• Standing instructions it cannot edit. Your instructions.md is read every session and never written to - enforced by the permission layer, not by prose asking nicely.
• Nothing installed into your other projects. All thirteen skills live in kingshand's own repository, so a Claude Code session anywhere else on the machine behaves exactly as it did before.

How a piece of work moves through it

1. You describe the work in the one session you talk to.
2. It writes a brief and waits for your word. Nothing is dispatched before you approve it.
3. It creates a git worktree inside the target repository, writes the worker's settings and marks the worktree trusted, so an unattended worker does not stop on a folder-trust dialog.
4. The worker runs as an ordinary interactive Claude Code session in a terminal kingshand owns, which is what lets it read a worker's screen while it runs and send text to one that has gone astray.
5. The worker leaves a report.md. That reaches the landing gate, and the landing gate reaches you.

Who it is for

Someone on Windows who already uses Claude Code and wants more than one piece of work running at a time without supervising each one by hand. It needs PowerShell 7, Git for Windows, Claude Code, and three small tools the installer fetches or names - the install page lists all six and what each is for.

What it is not

• It does not do the project work itself. It dispatches and supervises; the workers write the code.
• It is Windows only. Every script targets PowerShell 7 on Windows. On macOS or Linux the tool to use is firstmate by Kun Chen, which kingshand is a Windows-native rebuild of ideas from, and which does some things kingshand cannot.
• It is not a hosted service. You clone a repository and run it on your own machine. There is nothing to sign up for and no account.

Permissions, stated before you install

kingshand ships with Claude Code's permission prompts turned off for itself and for every worker it starts: neither will ask you to approve a tool call. That is deliberate - the session reads diffs, runs git and merges locally hundreds of times in a session - but it is a real decision, and better made knowingly. What still constrains it:

• Workers only ever run inside their own git worktree, never in your checkout.
• Nothing is dispatched into a repository you have not registered.
• Nothing pushes unless that project is registered with a push-capable posture, and nothing is merged for you at all - a pull request is where the work stops.
• Reads of ~\.ssh, AWS credentials and kingshand's own credentials directory are blocked, as are edits to your instructions.md.

If you would rather approve each call, the setting is one line in .claude\settings.json and removing it restores the prompts.

Where everything is

• Install and first run - the requirements, the commands, and what the installer writes outside the repository.
• Design decisions - the records kept about how workers are run and controlled, mirrored from the repository.
• llms.txt and llms-full.txt - this subdomain as plain text.
• emgee-labs/kingshand - the source, the tests, and the MIT licence.