Install
Kito is four programs:
| Program | What it does |
|---|---|
kito |
The command line |
kitod |
The daemon that records every save, one per repository |
kito-mcp |
The MCP server agents talk to |
kito-server |
One server for several repositories, for a team |
Your coding assistants
Section titled “Your coding assistants”After installing, the script looks for Claude Code, Codex and ZCode on
your machine and asks, for each, whether every new Kito project should
get it set up. The answer is kept: kito assistant default shows or
changes it, and kito assistant add <name> sets one up in a project at
any time. KITO_NO_ASK=1 asks nothing.
Platforms
Section titled “Platforms”- Linux and macOS.
- Windows (10 or later), as it is. In WSL too: keep your repositories
in the Linux file system there (
~/…), not under/mnt/c, where file events and lane copies are slow.
From a release
Section titled “From a release”curl -fsSL https://kito.sh/install.sh | shThe script takes the latest release on GitHub
for your platform, checks it against its SHA-256, and puts the four
programs in ~/.local/bin. KITO_VERSION=0.27.0 installs another
version, KITO_INSTALL_DIR another directory. The archives are on the
download page.
From source
Section titled “From source”You need git, a C compiler, and Rust 1.90 or later (rustup).
git clone https://github.com/KitoOrg/kitocd kitocargo build --release -p kitod -p kito-cli -p kito-mcp -p kito-serverThen put the programs on your PATH:
export PATH="$PWD/target/release:$PATH"Check it:
kito --versionOptional
Section titled “Optional”- Language servers, for renames that follow every use:
typescript-language-server,gopls,pyright,rust-analyzer,intelephenseandclangdare found by themselves when installed. - Linux 5.13 or later confines the checks of an integration and the commands run in a lane (Landlock): they write only in their own copy.
Next: First steps.