First steps
In a new directory:
kito initIn an existing git repository, bring its history in instead:
kito importBoth also set up your coding assistants. At a terminal, Kito looks for
Claude Code, Codex and ZCode on your machine and asks, for each, whether
to set it up here; the install script may have asked already, and
kito assistant default says it once for every project. Any assistant is
added later with one command:
kito assistant add claude # or codex, zcodekito assistant list # what this machine has, and how each is set up--no-assistants sets none up.
Every save is recorded
Section titled “Every save is recorded”From here on, every save is recorded by the daemon, kitod, which kito
starts by itself. There are no commits to make. To see what happened:
kito log b2bc7079 11-14 21:53 ada src/version.ts +1 −1 VERSION changed◆ ckpt#2 billing (git 78ff4e73aa) 928f6f58 11-14 21:53 claude src/billing.ts new invoice created [integrate lane/1: billing] 9239b953 11-14 21:53 ada src/auth.ts +10 −0, 7 saves getUser changed; getAdmin created◆ ckpt#1 start (git f908e3a85f)One line for each file worked on, however many times it was saved, with what
the saves meant for its functions. kito log -v gives every save a line of
its own.
Checkpoints
Section titled “Checkpoints”A checkpoint marks a point. It is also exported as a git commit:
kito checkpoint -m "first version"To go back to a checkpoint (recorded as new changes, so it can be undone):
kito rollback ckpt#1To set who signs the changes:
kito identity --name "Ada" --email ada@example.comFunctions keep their identity
Section titled “Functions keep their identity”In Python, JavaScript, TypeScript, Java, C#, C, C++, Go, PHP and Rust files, Kito follows the functions and classes: one keeps its identity when it is renamed, edited or moved to another file. Its whole story:
kito why --history src/users.ts:fetchUserNext: A first lane.