Coordinate several lines of coding work without losing the plot.
Start an auth refactor. Hand the tests to another agent, then chase an unrelated bug while both agents run. That should feel normal, not like a bookkeeping stunt.
kiki (kk) gives each line of work a thread. A thread combines a jj workspace, a tmux session, an agent session, and a live head in the repository history. Threads can follow one another. When a parent changes, kiki waits for the child agent to reach a safe boundary, updates its workspace, and tells the agent what moved.
kk new auth-refactor
kk new add-tests --follows auth-refactor
kk new investigate-login-bug
kk switch add-testsYou keep using jj, tmux, and gh directly. kiki handles the thread bookkeeping around them.
Important
kiki is pre-alpha. The design is written, but implementation has not started. There is nothing to install yet.
The reference book covers commands, safety rules, architecture, scope, and the roadmap. The orientation is the shortest tour of the planned first release.
Read the spec and open an issue if a design choice looks wrong or incomplete. This is the point when objections can still reshape the implementation.
The reference book is also a VitePress site. The site deploys to GitHub Pages from main, while pull requests run the same strict docs and production-build checks without deploying.
bun run docs:dev # local development server
bun run docs:check # links, contract terms, and production build
bun run docs:preview # preview the last production buildGitHub Pages must use GitHub Actions as its publishing source. The project-pages base path defaults to /kiki/; set VITEPRESS_BASE and VITEPRESS_SITE_URL when moving to a custom domain.
MIT © 2026 Sandile Keswa