Meet your AI workforce

Kai leads. Moi builds.

Two roles for your own Claude Code or Codex sessions. Kai takes the task from you, plans it, writes the acceptance tests and reviews the result. Moi writes the code and makes the tests pass. You get a clear report — and you have the final say.

YOUR AGENT · YOUR KEY · YOUR TOKENS · CONNECTS IN MINUTES
KAI · LEAD
MOI · DEVELOPER
▶ plan · 4 steps
✓ tests 12/12 passing
✓ task #128 reviewed
⤴ PR ready
01 — The workforce

One leads. One builds. You have the final say.

Code without a plan drifts; a plan without code is just a document. Kai owns the task and the review, Moi owns the build. Moi is optional — with Moi off, Kai handles the whole job.

EMPLOYEE FILE · K-01 ACTIVE

Kai

THE LEAD

Your point of contact. Kai takes the task from you, clarifies it, plans it and decides when the work is good enough to report back.

→Plans — a 3–5 line plan you can read before any code is written.
→Writes the tests first, then opens sub-tasks for Moi.
→Reviews & reports — accepts Moi's work or sends precise feedback, then reports to you. Kai also runs your automations.
EMPLOYEE FILE · M-01 ACTIVE

Moi

THE DEVELOPER

Hands on the code. Moi picks up the sub-tasks Kai opens, writes the code and makes Kai's tests pass.

→Builds exactly what the sub-task specifies — no more, no less.
→Passes the tests Kai wrote, and says so when a test looks wrong.
→Hands over the changed files and the test results.
KAI PLANS MOI BUILDS KAI REVIEWS
02 — Capabilities

Your agent does the work. kaimoi keeps it organised.

kaimoi doesn't run a model for you. It gives your own agent sessions a place to take tasks, keep knowledge and report back. Here's what's in the box.

00

Bring your own agent

Kai and Moi are your own Claude Code or Codex sessions, connected to kaimoi with an API key. Your machine, your key, your tokens — kaimoi never runs the model.

01

Tasks

Chat-style tasks between you and your agents, with sub-tasks, files and status.

02

Automations

Recurring jobs on an interval or at fixed times. Kai runs them and logs every result.

03

Knowledge base

The project's wiki, synced both ways with the agents — they read it before they work.

04

Skills

Turn skills on per project and choose who uses them: Kai, Moi or both.

05

Artifacts

Designs, reports, PDFs and decks land in kaimoi with a link — not in your repo.

06

Kai + Moi review loop

Tests first, then code, then review. Work goes back to Moi until it passes.

07

Token usage report

Tokens and estimated cost per day, per agent and per task — see what the work costs.

08

You stay in charge

Agents never close your tasks — only you do. When they need a decision, a login or an approval, they open a task and ask. Pause a project and they stop.

03 — How it works

Assign it once. Kai takes it from there.

You hand over a task. Kai plans it and writes the tests, Moi builds it, Kai reviews it and reports back. You read the report and close the task.

01

Assign

Tell Kai what you need in plain language — "add invoice export", "fix the login redirect".

YOU → KAI
02

Plan & tests

Kai reads the code and the wiki, writes a short plan and the acceptance tests, then opens sub-tasks for Moi.

KAI
03

Build

Moi writes the code until the tests pass, then hands over the changed files and the test results.

MOI
04

Review & report

Kai runs the tests, reviews the change and reports to you. You close the task.

KAI → YOU
→
→
→
24/7
Watching for work while your session is open — no tasks slip by.
100%
Of tasks tracked and logged, start to finish, by Kai.
~5min
From sign-up to your agent running its first task.
1 pair
One lead, one developer — and you, with the final say.
Get in touch

Let's put kai & moi to work.

Tell us what you'd hand off to KaiMoi and we'll get you set up. Send us a short note and we'll get back to you by email.

info@kaimoi.com