Single compose tool
Kit exposes one tool, compose, rather than many separate agent tools. The compose program can read files, run tests, apply edits, retry failed commands, and return structured data in a single round trip.
Kit
Kit is a coding agent runtime for terminal and compatible editor workflows, supporting ACP, A2A, MCP, long-running sessions, subagents, and model choice.
Overview
Kit is a coding agent runtime that gives the model one tool for writing and running programs. It ships as a terminal client, an Agent Client Protocol (ACP) server, an A2A endpoint, and a subagent orchestrator in one static binary.
The project positions Kit as a lower-friction alternative to agent harnesses that expose many tools. Instead of many round trips, Kit centers work on a single compose operation written in Runlet, which can read files, run commands, edit code, and coordinate subagents while returning structured output.
Features
Composable Runlet programs
The runtime supports shell, edit, subagent, prompt, fork, tool_search, tool, auth, skill, a2a, and docs calls inside Runlet programs. Independent calls can run concurrently, with data dependencies and after blocks used to control order.
Reusable subagents
Subagents are first-class values that can be continued, forked, inspected, or closed. The documentation also says you can require JSON matching a schema and use Claude Code, Codex, Cursor, or Kit as the subagent harness over ACP.
Open protocol support
Kit provides ACP v1 and v2 over stdio, HTTP/SSE, and WebSocket, plus A2A v1 in both directions. It also supports MCP, Agent Skills, and Agent Plugin packages.
Long-running sessions
The runtime keeps an append-only JSONL transcript on disk, compacts context automatically at 80% of the window, and lets you resume sessions from tui, prompt, or any ACP client.
Model and provider choice
Kit supports ChatGPT subscriptions through native OAuth, and it can also use models through OpenRouter and the Speakeasy AI Control Plane. The /model command changes the model during a session.
Use Cases
Run multi-step coding tasks in one agent turn
Use Kit when you want a coding agent to do more than call individual tools one at a time. The compose program can bundle reads, edits, tests, retries, and subagent delegation into one workflow.
Connect Kit to compatible editors and clients
Use the ACP server when you want Kit to plug into editors or other ACP-compatible clients. The repository states that ACP separates clients from runtimes, which reduces the need for custom integrations.
Work interactively in a repository
Use the terminal UI or prompt command for interactive project work. The README shows starting a session against a project root, then either continuing in tui or running a one-shot request that returns a session ID.
Run Kit as a headless runtime
Use the headless server mode when you need Kit available over remote ACP or HTTP. The quick start includes a serve command with options for remote ACP, HTTP, and disabling local stdio or A2A as needed.
Bridge multiple agent protocols and harnesses
Use Kit’s protocol support when you need to coordinate with other agent systems or reusable tools. The docs explicitly mention A2A, MCP, Agent Skills, Agent Plugin packages, and subagents over ACP.
Pros and Cons
Pros
- One compose tool can cover file reads, tests, edits, retries, and structured output in a single request.
- ACP support makes the runtime usable in compatible editors and other ACP clients without custom integrations.
- Subagents are reusable and can be continued, forked, inspected, or closed.
- The runtime supports multiple protocols and ecosystem pieces, including ACP, A2A, MCP, Agent Skills, and Agent Plugin packages.
- Session state is persisted to disk and can be resumed, with automatic context compaction for longer runs.
Cons
- Kit is not a security boundary; the documentation says it has no permissions framework, sandbox, or web UI.
- The install script is documented for macOS arm64 and Linux x86-64, so platform coverage is not stated beyond those targets.
FAQ
How is Kit installed?
Kit is installed as a static binary. The README shows an install script for macOS arm64 and Linux x86-64, a Docker image, and a source build path using the Rust toolchain in the repository.
What integrations or protocols does Kit support?
Kit is designed to work through ACP, so it can run in compatible editors and ACP clients. The README also says it supports A2A, MCP, Agent Skills, and Agent Plugin packages.
What does Kit do in practice?
The README describes Kit as a runtime with a terminal client, an ACP server, an A2A endpoint, and a subagent orchestrator. It is meant to coordinate coding work through the compose tool and Runlet programs.
Are there any important limitations to know before using Kit?
Kit is not described as a security boundary. The README says it has no permissions framework, sandbox, or web UI, and that it should run inside a security boundary you trust.
Can Kit be used in different workflows, including team or editor-based setups?
The documentation includes quick-start commands for logging in with OpenAI, OpenRouter, or Speakeasy, then launching the terminal UI, running one-shot prompts, or serving ACP for editors and clients.
Quick Facts
- Category
- Developer Tool
- Product type
- Coding agent runtime
- Source domain
- github.com
- Core interface
- Terminal client and ACP server
- Supported protocols
- ACP v1/v2, A2A v1, MCP
- Primary users
- Developers working with coding agents and compatible editors
Kit Alternatives
ByteAsk
ByteAsk is a terminal-first AI coding agent for C and C++ that edits repos and verifies changes with compilers, debuggers, sanitizers, and tests.
Ghost
Ghost is a terminal-based AI assistant for chatting, code generation, and CLI tasks. Includes free models, supports Linux, macOS, Windows, and is open source.
Vi3ecode
Vi3ecode is a maintained development environment for AI coding agents, keeping project context, terminal, Git, memory, flows and review connected.
Lucid Train
Lucid Train is a local-first AI coding harness that turns repo code into architecture diagrams for coding agents. Desktop app and Rust CLI, local models or API keys.
CreateOS Sandbox
CreateOS Sandbox is an isolated compute environment for running code and agent workloads in Firecracker micro-VMs with private networking and SDK, CLI, or MCP control.
hob
hob is an independent workspace for coding agents, with local control over sessions, terminals, history, routing, and follow-up work.