on-prem · durable · sandboxed · bring your own harness
The on-prem, durable runner for coding agents. Bring your own harness, define agents as files, and run each one sealed and checkpointed.
$ kimoto run "investigate job 123 failure, post in #team-data-pipelines" ↻ agent triage · harness claude-code · run r_8f3a → pulled logs for job 123 (exit 137 — OOM) → traced to spark executor memory ceiling → drafted fix + summary ✓ posted to #team-data-pipelines durable · resumable · 14.2s
ご注文 · "your order" · CLI · Slack · Webhook
Same kitchen underneath. A shell command, a Slack mention, and an alert webhook all land in the same durable queue, and each one reports back to wherever it came from.
Hand an agent a task in plain language and close the laptop. It runs durably and reports back when it's done.
$ kimoto run triage \ "why is checkout p99 up?"
Mention kimoto in any channel. It answers in the thread with full context from your codebase.
@kimoto how does feature x work?
↳ feature x lives in billing/x.ts…
Wire kimoto to your paging. A Datadog alert can have an agent investigating before anyone opens a laptop.
▲ datadog alert
latency_p99 > 800ms
→ kimoto: oncall-investigate
弁当 · 個室 · 貸切 · three rooms
Isolation isn't a mode you turn on. It's where every run starts. An agent begins in a sealed box and gets exactly as much room as the job needs, all of it on your metal.
ご注文 · the order
analytics: "which customer placed the largest order after the pricing change?"
run r_9d21 · claude-code · searches + python
火加減 heat
4s flame
器 vessel
256 MB
出前 delivery
準備中 · closed
お勘定 · the verdict
送り返し = sent back · resumed from the last good step
inside the 弁当 · code mode
In the box, an agent doesn't call tools one at a time. It writes the plan as code: searches, analytics, scrapes, whole subagents fanned out with a loop and gathered back with a comprehension. If you can express it in code, an agent can do it in code mode.
And because every bridge call and every spawn() runs as a durable step, the whole thing is deterministic and replayable. Kill the box mid-fan-out and the run resumes with every finished subagent's work intact.
sealed · deterministic · ms start
# largest order after the pricing change? orders = mcp.shop.orders(since="2026-06-12") # bridge · allowlisted checks = [kimoto.spawn("verify", o) for o in top(orders, 20)] # deterministic fan-out best = rank([c.result() for c in checks], by="order_total")[0] mcp.slack.post("#revenue", render(best)) # bridge · journaled ✓ 20/20 verified · resumable at every call
おまかせ · "I'll leave it to you"
Omakase means handing the whole course to the chef. A kimoto workflow is the same move: compose deterministic steps and agent steps, hand it over once, and walk away. Each step checkpoints, so a workflow can pause for hours, survive a deploy, and pick up exactly where it stopped without re-running anything that already succeeded.
today's course · pr-review
Fetch PR 123
deterministic
Run the test suite
deterministic · retry-safe
Review the diff
agent · claude-code
Post the verdict to Slack
deterministic
いつもの · "the usual"
A flow is a standing order. Describe it in a sentence and kimoto compiles it into durable, scheduled steps, deciding for itself whether each one is deterministic code, a notification, an agent, or a whole other flow. It ticks away on your infrastructure until you say otherwise. And since every step is checkpointed, a crash mid-tick never loses work and never doubles it.
compiled · flow f_1c22
tick 412 ↻
Every 2 minutes
schedule
check_ingest_metrics()
deterministic · retry-safe
Anything look off?
condition
├ no → sleep till next tick ↻
└ yes → continue ↓
Triage investigates
agent · claude-code
Page #oncall with findings
notify
Severe? Spin up rollback-canary
flow → flow
durable · scheduled · self-routing
創業 · since the first batch
from the house ledger · vol. 1
The house was opened by a platform crew, the kind every company has one of if it's lucky. For years they kept other people's agents alive. They restarted the stuck ones at 3 a.m., replayed the lost ones, mopped up the half-finished. They built the queues and the traces and the dashboards nobody thanks you for. They got very good at it, and eventually very tired of watching good agents die of bad plumbing.
One of them brewed sake at home, the old way. Kimoto (生酛) is the slow method. No dosed acid, no shortcuts. You raise a starter that makes its own defenses and fends off everything else, working in the dark, mostly unattended. The culture that comes out the other side is famously hard to kill.
That, they decided, was the kitchen worth building. Runs checkpoint like batches in a vat. Agents cook in their own sealed rooms. And the first starter never left. It still sits behind the counter, bubbling through the night shift, a little of it in every batch the house sends out. Everyone just calls it Moto.
seal it · set it working · go home
yaakov shaul
杜氏 tōji · raised the first starter
sahand saba
棟梁 tōryō · built the house
junyuan zheng
板前 itamae · plates everything
cody lundquist
焼き方 yakikata · the grill never cools
One binary on your own machine. Point it at a harness, write an agent file, and start your first batch.