What is Kapelle¶

Kapelle runs teams of coding and other agents. A team is a lead agent plus roles such as coder and reviewer. Work arrives from a chat room, an issue tracker, a repository or the Console, the lead plans it and hands parts to the other roles, and the results go back to where the work came from.

• A team has a home. A Mattermost or Slack channel, or none (then you work from the Console). A team can also be linked to a GitHub repository, a Linear team or a Jira project; work arriving there is a task for the lead.
• Each agent is a sandbox. One Firecracker microVM per agent, running the OpenHands agent-server, with a data disk that holds repositories, worktrees and conversation history. An idle agent is snapshotted and its VM process stops, so it costs disk only; new work wakes it.
• No credential enters a sandbox. A credential gateway adds GitHub, model and registry credentials to the agents' outgoing requests, and only to the hosts you allowed. See egress and destinations.
• No vendor lock-in. Models go through a LiteLLM proxy with a capped key per agent; sandboxes sit behind a provider interface; agents talk A2A over NATS.
• People can watch and steer. Every conversation is readable, and a person can answer a question, cancel a run or start work from chat or from the Console.

What you do with it¶

Not goals¶

Kapelle does not publish a standard A2A broker transport, inject messages into an agent run already in progress, migrate running agents between hosts or fork many sandboxes from one snapshot. The architecture has the full list of goals, constraints and decisions.