kndl

Multiplayer agentic sessions.

kndl is a self-hosted Hub for Claude Code Sessions. Each Session works in its own Sandbox on a machine you own. Whoever starts it drives it, and everyone with access to its Repo can watch it live.

$ curl -fsSL https://raw.githubusercontent.com/kddige/kndl/main/install.sh | sh

macOS or Linux, with git. What it installs

Get startedGitHub

SandboxRunnerSession
kndl's web UI: a Session named Retry payment calls on timeout, active, with three Participants. Claude is mid-Turn, two prompts wait in the Prompt queue with Steer buttons, and a Runners and Environments sidebar lists the Repos.

What kndl does

Sessions you share

Everyone with access to a Repo can open its Sessions and follow Claude live. The person who started one drives it: their prompts wait in a queue, or join the running Turn withSteer.

Work in a Session

A Sandbox per Session

Claude Code and every command it runs live in a microVM, built from the Repo's Environment. Nothing runs on the host.

Environments

On your machines

The Hub is one Bun process with a SQLite database. Runners are your Macs and Linux boxes, and they connect to the Hub, not the other way round.

How kndl works

Your own Claude

Each person adds their own Claude setup token once. Only the Sessions they start run on it, and only they prompt them.

The security model

Try it, then remove it

Run the Hub and a Runner on one machine, start a Session on one of your Repos, and take it all away with one command. About 10 minutes.

QuickstartDeploy for a team

# install
$ curl -fsSL https://raw.githubusercontent.com/kddige/kndl/main/install.sh | sh

# set up a Hub and a Runner, and answer its questions
$ kndl onboard

# remove it all
$ kndl uninstall --purge