Welcome to Kleio
Engineering memory for teams building with humans and AI.
Kleio captures the decisions, checkpoints, and work signals that flow through your editor, your CLI, your agents, and your repos — and turns them into a structured, queryable history of why the codebase looks the way it does.
These docs are the fastest path from "I have a Kleio account" to "my workspace is capturing real signals from real work." If you don't have an account yet, start at kleio.build.
Status: Beta. The product is live at app.kleio.build on Free, Pro, and Team plans. Docs reflect the current shipping behavior; the Status / roadmap section of the org README has the public roadmap.
How to read these docs
- Onboarding — the five-step path to a working install: sign in, configure repo access and signals, optionally import history, install the CLI, set up your editor. Read top to bottom on your first day.
- Concepts — short pages explaining how Kleio thinks. Read these once you've captured something and want to know what's actually happening underneath.
- Reference — pointers to the canonical READMEs for the CLI, MCP server, and GitHub integration. The repos are the source of truth.
If something here is wrong or out of date, file an issue or PR at github.com/kleio-build/kleio-docs.
What you'll set up
By the end of Onboarding all four pieces are running and your first capture is visible in the web app.
Where to go next
- New here → Onboarding › Sign in & GitHub App
- Want to understand what gets captured → Concepts › Primitives
- Auditing what Kleio reads from your repos → github.com/kleio-build/kleio-github
- Need help → info@kleio.build