TERMINAL-NATIVE · EVENT-SOURCED · POWERED BY ANTHROPIC

An autonomous engineer whose every decision is an event you can replay, fork, and diff.

KHAELOR designs before it implements, verifies before it claims done, and writes every action — even the ones at 3 AM — into an append-only log you can audit. Autonomy without auditability is scary. KHAELOR sells auditable autonomy.

$ curl -fsSL https://www.khaelor.sh/install.sh | sh
40durable event types
11powerful tools
698tests, all green
0invented numbers
Understand first. Design second. Implement third. Verify always. Even at 3 AM.
One session, start to finish
khaelor — ~/dev/my-project
 KHAELOR ▸ my-project · main

  fix the memory leak in the renderer

 ├─ symbols "RenderBuffer" · 3 hits · 12ms
 ├─ refs appendLine · callers · 14 sites
 ╰─ read src/tui/render.ts · 240 lines

  design submitted · 2 files · replace growing buffer with a ring
 ✓ design auto-approved · 2 files

 ├─ edit src/tui/render.ts  +31 −12
 ╰─ edit src/tui/buffer.ts  +8 −3

  verify   typecheck  1.2s · tests  4.1s · lint 
 ✓ verified 4.1s

  IMPLEMENT  main  sonnet  ▰▰▰▱▱▱▱▱ 38% │ in 45k · out 3.2k
Not another coding agent

◐◑● Phase gates

“Understand → design → implement” is a runtime mechanism, not a slogan. Write tools stay locked until a design artifact — goal, approach, files, risks, verification — is approved. Small designs auto-approve; big ones ask you. --gate strict|auto|off.

Native verification

After each edit batch, KHAELOR runs your typecheck, tests, and lint itself — in parallel — and repairs failures in a bounded loop before handing back. No PR-shaped guesses: .khaelor/verify.json or auto-detected.

Fork · replay · sdiff

Every session is an append-only event log. /fork any checkpoint, /replay a run against another model in a throwaway worktree, then /sdiff the two runs — turns, tool calls, files, tokens. Run it twice, diff the runs.

Semantic index

A RepoGraph over your codebase: symbols finds definitions with signatures, refs maps callers, callees, and importers before an edit. Skeletons instead of whole files — exploration for a fraction of the tokens.

Memory with provenance

The agent maintains .khaelor/MEMORY.md itself — conventions, commands, pitfalls — and every entry is anchored to the exact session and event that produced it. You always know why it believes something.

Parallel worktrees

/spawn runs subtasks in isolated git worktrees with attenuated capabilities and their own child sessions. Supervised --no-ff merges; conflicts abort cleanly. Your working copy is never touched.

The interface

No spinner theater, no screen flicker — a print-once scrollback, a bounded live region, and a 16 ms frame budget. Here is what your day actually looks like.

khaelord — the engineer that lives

A persistent daemon with structured, event-sourced goals — not a prose checklist. Each run gets a throwaway worktree, phase gates even at night, mandatory verification, hard budget ceilings, and an asynchronous approval queue: a suspended run costs zero.

khaelord — 3 AM, fully audited
 $ khaelord goal add "keep npm deps fresh without breaking changes" \
     --type maintain --schedule "0 6 * * 1" --budget 5 --escalation draft-pr

 $ khaelord start
 khaelord running — project ~/dev/my-project

 03:12  goal deps-fresh check failed → run r7f2 in worktree khaelor/goal-r7f2
 03:14  design recorded · 3 files · in the log, replayable
 03:17 ✓ verified · typecheck ✓ tests ✓ · branch left for review
 03:17 spent today: $1.84 / $20 · runs 1/8

Other agents give you an assistant that lives. KHAELOR gives you an engineer that lives — and whose every nocturnal decision is an event you can replay, fork, and diff the next morning.

understand · design · implement · verify always — even at 3 AM

Approval, when it matters
design panel — strict mode
 ╭─ ◑ DESIGN — approval required ─────────────────────────╮
  Goal      Fix the renderer memory leak               
  Files     src/tui/render.ts · src/tui/buffer.ts     
  Approach  Replace the growing buffer with a ring…    
  Risks     ▪ scrollback regression (medium)           
  Verify    vitest run tests/tui + manual demo         
 ├────────────────────────────────────────────────────────┤
         [a] approve   [r] reject                       
 ╰────────────────────────────────────────────────────────╯
Everything is real
KHAELOR
Costs & tokenssummed from real API usage metadata — never estimated, never invented
Test resultsyour own commands, real exit codes, errors-first truncation
Historyappend-only JSONL, torn-write recovery, byte-exact replay
Permissionscapability-based (file.write.project, git.modify, network.access…), deny > ask > allow, silence is never consent
3 AM decisionsone event log per goal run — Enter on a run replays exactly what happened
Start
curl -fsSL https://www.khaelor.sh/install.sh | sh
export ANTHROPIC_API_KEY=<your key>
cd your-project
khaelor
Getting started → Cookbook → All commands → FAQ →