Skip to content
kndlkndlkndl

Introduction

kndl (said “kindle”) runs Claude Code Sessions on machines you own. Whoever starts a Session drives it, and your team watches it live from the browser.

A Session in kndl's web UI. Claude is mid-Turn: a subagent searches the docs in the background, tool calls are listed with their results, and Bob's prompt waits in the Prompt queue with a Steer button.

What you get

Section titled “What you get”
  • Shared Sessions. Everyone with access to a Repo can open its Sessions and follow Claude live. A Session’s Creator drives it: their prompts sent while Claude works wait in a Prompt queue, or join the running Turn with Steer.
  • A Sandbox per Session. Claude Code and every command it runs live in a microVM on a Runner, never on the host.
  • Your machines. The Hub and the Runners are yours: a laptop, a Mac mini under a desk, a Linux server. Nothing runs on a kndl service, because there isn’t one.
  • Your Claude account. Each person adds their own Claude setup token, and the Sessions they start run on it, on any Runner. Nobody else’s prompts reach it.

How it fits together

Section titled “How it fits together”
How kndl fits togetherPeople open the Hub's web UI in their browsers. Runners on your own machines connect to the Hub. Each Runner runs Sessions, each in its own Sandbox with Claude Code inside.PeoplebrowserbrowserbrowserHubweb UI · Sessionssign-in · SQLiteconnectRunner · studioSandboxClaude CodeSandboxClaude CodeRunner · build-boxSandboxClaude CodeSandboxClaude Code
Runners connect out to the Hub, so the Hub never reaches into your machines. Each Session runs in its own Sandbox on a Runner.
  • The Hub is one Bun process with a SQLite database. It serves the web UI, signs people in with GitHub, and keeps every Session.
  • A Runner is a machine that runs Sessions: a Mac with Apple Silicon, or Linux with KVM. It connects to the Hub, so the Hub needs no access to it.
  • A Sandbox is the microVM a Session runs in, built from its Repo’s Environment: an image and a setup script.

One machine can be the Hub and a Runner at once. That’s how the Quickstart runs it.

Who it’s for

Section titled “Who it’s for”
  • You, trying it. Install it on one machine, start a Session on one of your Repos, and remove it with one command if it isn’t for you.
  • A team. Run the Hub on a server, add a Runner or two, and invite the people who work on your Repos.

What it isn’t

Section titled “What it isn’t”
  • Not a hosted service. You run every part. There’s no account to make and nothing to pay kndl for.
  • Not a fork of Claude Code. kndl runs Claude Code as Anthropic publishes it, on your Claude account and under Anthropic’s terms.
  • Not affiliated with Anthropic. kndl is an independent open-source project. Claude and Claude Code are trademarks of Anthropic, PBC.
  • Not finished. kndl is early. Expect settings to change between Releases.

Next steps

Section titled “Next steps”
QuickstartRun kndl on one machine and start a Session, in about 10 minutes.
Deploy for a teamPut a Hub on a server, add Runners and invite people.
How kndl worksThe Hub, Runners, Sandboxes, and who drives a Session, in detail.

kndl is an independent project. It is not affiliated with or endorsed by Anthropic. Claude and Claude Code are trademarks of Anthropic, PBC. About kndl