Early Access Coming 2027

Kaizen: Terminal AI coding agent

Every change remembered.
Every mistake reversible.
Every session continuous.

You work at the Helm.

Single binary. SQLite-only. No cloud backend. Works with any LLM provider.

Effort levels: low · medium · high · ludicrous · auto

A real Kaizen session working on a small demo Go service. Helm plans, Scout reports back and Cody is writing the change.

You Work at the Helm

Helm is Kaizen's coordination layer. It classifies every request, builds a plan, and delegates to specialist agents - but only after confirming scope for anything non-trivial. You stay in control.

  • Helm plans before acting - confirms scope for large changes
  • Delegates read tasks to Scout, write tasks to Cody, reviews to Sage, docs to Scribe
  • Helm never edits files directly - pure coordination
  • Confirmation gate scales by scope: trivial → proceed, large → plan first

See It in Action

Real captures of the Kaizen terminal UI, run against a small demo project. Click any image to enlarge.

One request, three specialists, one checkpoint. Helm summarises what changed and the verification run passes.
The command palette (Ctrl+K): restore a checkpoint, switch model, set a budget cap or export the session.
kaizen undo previews every file it will revert or remove, and saves your current state first.

Your Agent Remembers Everything

Kaizen persists decisions, discoveries, and bugfixes in SQLite across every session. FTS5 full-text search with staleness detection keeps your context fresh - no re-learning, no cold starts.

  • FTS5 full-text search across all sessions
  • Staleness detection flags outdated memories
  • Typed memories: decisions, bugfixes, discoveries and architecture notes
  • No vector database required

Every File Write, Checkpointed

Before Kaizen writes or edits any file, it CAS-snapshots the previous state. Made a mistake? kaizen undo shows a numbered list, diff preview, and y/N confirmation. No AI mistake is permanent.

  • Pre-write CAS snapshots on every file operation
  • Preview exactly which files will be reverted, recreated or removed before you confirm
  • Every restore first saves your current state, so you can undo an undo
  • Named savepoints for manual checkpoints
  • Automatic verification - after edits, Kaizen detects and runs your build and test commands, feeding failures back for a fix pass

Parallel Agents, Not Parallel Promises

Helm plans the work and spawns Scout, Cody, Sage, and Scribe as separate OS processes by default, each with its own TUI tab and independent scrollback. An in-process mode runs them as goroutines that share the orchestrator's database and LLM client when startup latency matters.

  • Helm orchestrator with create_plan / update_plan tools
  • Scout (search), Cody (write), Sage (review), Scribe (docs) specialists
  • Up to 8 agents per session, with the number running at once configurable
  • Per-agent TUI tabs - click to reactivate, × to close
  • Effort levels: low · medium · high · ludicrous · auto - adjusts turn budgets and thoroughness
  • Sage returns structured PASS / FAIL / CONDITIONAL verdicts, triggering Cody retry loops
  • Plan-step checkpoints: every completed plan step creates a named savepoint automatically
  • Dependency-aware planning enforces one writer per file - edits to the same file are grouped into a single Cody spawn and dependent batches are sequenced
  • Delegate to external CLI agents: Helm can spawn Claude Code, Aider or any command, translating its output into the shared event stream

Understands Your Code Structurally

Kaizen builds a symbol index across your entire codebase. The repo_map ranks files by how often they are referenced so agents know what matters before reading a single line.

  • Symbol index across 18 languages
  • repo_map ranks files by reference count - agents prioritise what matters
  • Symbol and reference lookups let agents find code without reading whole files
  • Incremental indexing: auto-reindex on every write, background watcher for external changes

Context That Never Disappears

Other agents summarise old context and discard it. Kaizen replaces tool output with CAS hash references - the agent can recall any masked content on demand. Old tool output is masked rather than summarised away.

  • Masked tool output is stored and recoverable
  • recall tool retrieves any masked content instantly
  • Kicks in automatically as the context window fills
  • Summarisation only as a last resort

"Memory + checkpoints + smart routing: a focused model with full project context can outperform a frontier model with none."

Works With Your Entire Stack

Point Kaizen at any LLM provider - or point it at a local endpoint.

Built to Run Anywhere

Language Go 1.26
Storage SQLite
Cloud Required None
Distribution Single binary
Platforms Linux, macOS, Windows (amd64 + arm64)
Context Window Up to 200K tokens
Languages 18 supported
Built-in Tools 35
Safety Modes permissive · standard · restricted
Cost Control Per-session budget cap
LLM Providers Anthropic, OpenAI, any compatible endpoint
Effort Levels low · medium · high · ludicrous · auto

Frequently Asked Questions

What is Kaizen?

Kaizen is a terminal-first AI coding agent with persistent cross-session memory, CAS-backed undo on every file write and multi-agent orchestration. It ships as a single binary with no cloud backend and works with Anthropic, OpenAI and any compatible LLM endpoint. The Helm orchestrator coordinates specialist subagents: Scout for search, Cody for writing, Sage for review and Scribe for documentation.

Who is Kaizen designed for?

Kaizen is designed for software engineers and teams who want an AI coding agent that runs entirely on their own infrastructure, remembers context across sessions and gives them a reliable undo path for every AI-driven file change. It suits developers who prefer the terminal, want cost control via per-session budget caps and need to keep code and context on their own machines.

When will Kaizen be available?

Kaizen is currently in Early Access, with general availability due in 2027. Join the waitlist to get priority early access and a direct feedback channel into development.

What makes Kaizen different from other AI coding agents?

Three features set Kaizen apart. First, cross-session SQLite memory with FTS5 full-text search carries decisions, bugfixes and architectural discoveries from one session into the next. Second, every file write is checkpointed before it happens, so kaizen undo lists numbered checkpoints and previews exactly which files will change before you confirm. Third, Helm coordinates specialist agents (up to eight per session) as separate OS processes with their own TUI tabs, dependency-aware planning and Sage review verdicts.

What LLM providers does Kaizen support?

Kaizen works with Anthropic, OpenAI and any OpenAI-compatible endpoint. You can also point it at a local OpenAI-compatible endpoint, and Kaizen has no cloud backend of its own.

How do I get early access to Kaizen?

Join the Kaizen waitlist to register for early access and shape the product through direct engineering feedback. Join the waitlist.

Get Early Access to Kaizen

Join the waitlist. Shape the product with direct engineering feedback.

Priority early access
Direct engineering feedback channel
Roadmap influence

Rolling out AI coding agents across your teams? See Advise.