From curious to installed in one coffee.
Five commands. Free. Nothing leaves your terminal. It starts with npx timo scan — read-only, no signup, no workspace — and ends with a gate in your CI.
⟁ timo · scanning 5,412 files · read-only · 4m 12s
READINESS 62 · C+ · AGENT-RESISTANT — 6 dimensions
→ fix plan ready · next: timo initexample output
scan → init → memory → docs → check.
That’s the whole surface. Each one writes plain files into your repo — or, in the scan’s case, writes nothing at all. No dashboard required. No lock-in possible.
timo scan
The Agent-Readiness Scan, from your terminal. Six scored dimensions — code health, documentation, agent memory, review & control, tests & environment, agent config — roll up into your Readiness Score, with a fix plan. Read-only. It writes nothing and sends nothing.
FREE⟁ scanning 5,412 files · read-only
✓ code health — 26 findings (4 high)
✓ documentation — 3 of 12 domains covered
✓ agent memory — none found
✓ review & control — unreviewed merges found
✓ tests & environment — 7 flaky tests
✓ agent config — no CLAUDE.md / AGENTS.md
READINESS 62 · C+ · fix plan → timo initexample output
timo init
Stamps memory, docs, standards, and gates into the repo — as a PR your team reviews. Seeded memory lands marked UNVERIFIED until a human promotes it. Nothing lands unreviewed, including our own files.
FREE✓ .timo/memory/ — 6 seed notes (UNVERIFIED — you promote)
✓ .timo/docs/ — architecture map + 12 domain stubs
✓ CLAUDE.md + AGENTS.md — agent config for your stack
✓ .timo/standards/ — your team’s rules, as files
✓ ci: timo-check.yml — the gate, wired in
→ branch opened · your team reviews the PRexample output
timo memory
Creates verified memory notes, module by module — every claim cited to file:line or flagged TBD. Invention is a bug. This is what stops agents re-deriving your codebase every session; teams see 40–65% token reduction after memory install.
FREE⟁ reading module · drafting note…
✓ payments.md — 34 claims · 31 cited to file:line · 3 flagged TBD
a claim cites the line that proves it — or says TBDexample output
timo docs
Generates living documentation for the humans — new hires, reviewers, on-call. Cited or flagged, like memory. And kept true by the gate: once registered, a doc that drifts from the code fails timo check.
⟁ generating from code + memory…
✓ 12 domain docs written — every claim cited or flagged
✓ registered with the gate — stale docs now fail timo checkexample output
timo check
The conformance gate. Runs locally before you push and in CI on every PR. Broken citations, stale memory, leaked secrets, missing structure — it fails loud and says exactly why. It never guesses and it never rubber-stamps.
FREE✗ FAIL — 2 citations point to lines that no longer exist
→ docs/payments.md:41 · memory/orders.md:17
fix the claim or flag it TBD — the gate never guesses
$ timo check (after fix)
✓ PASS — structure · citations · secrets · freshnessexample output
The same gate, on every PR.
What you run locally as timo check runs in CI on every pull request — same rules, same output. And it’s vendor-independent: the check holds no matter which agent wrote the code — Claude Code today, Cursor tomorrow, whatever ships next year.
One gate, not one per tool
The check lives in CI, not inside any coding agent. Switch agents, add agents, mix agents — the gate doesn’t care who wrote the diff.
Fails loud, never guesses
A failing check names the file, the line, and the rule. No score-shrug, no “looks fine.” Fix the claim or flag it — those are the options.
Memory that can’t go stale
Because the gate blocks merges on broken citations, memory and docs stay current the same way tests do: the build makes them.
Free is complete, not a trial.
All five commands are free for getting started — no seat limits on the CLI, no expiring features. The line we run the business on: the tool is free, the people are paid. Paid begins only when you want the whole company moved, not when you want the tool to keep working.
What “free” means in practice
- Everything the CLI writes is committed to your git
- The scan is read-only — nothing leaves your terminal
- Cancel nothing — there's no account to cancel
- Your code, your systems, your IP
The platform is free because everything it creates lives in your repos. We can’t lock you in, so we don’t try — we earn the paid work by being the people who know your codebase best.
The CLI is the front door. Here’s the house.
Timo Memory & Docs
What timo memory and timo docs build: a verified, cited, living record of how your system works.
Read more →Timo Gates
What timo check grows into: every AI change checked against what you asked for, before it merges.
Read more →The same brains, inside your agent
Everything the CLI installs also works inside Claude Code, Cursor, and Codex — memory surfaces mid-conversation, the gate speaks at commit time.
Watch a session →One command. Five minutes. Your Readiness Score.
Read-only. No signup, no sales call, nothing written to your repo.