A durable core for TypeScript agents.
An open source framework for building agents that pause, crash, resume, and stay correct. The entire runtime is capped at 2,000 lines.
npm i @vincemakes/kiso-core
Small enough to read. Durable enough to leave running.
Most agent frameworks ask you to trust a runtime you will never finish reading. kiso takes the opposite bet: keep the part you have to trust small, and put everything else in packages you can ignore.
Lines in the core, as of v0.1.30
The cap is real. CI counts the kernel before it installs a single dependency, and a pull request that pushes it over gets closed no matter how good the feature is. When something needs more room it grows as a package instead. That is the point, not a workaround.
What a running agent is expected to survive
Every session is an append-only event log on disk. Approvals outlive the process that asked for them, tool calls leave durable receipts, and a resumed run continues from the exact point it stopped rather than starting the turn again.
Seven packages, 636 tests, and 32 decision records explaining why each thing is the way it is.
kiso code
The coding agent built on that core, and the reason the core exists. It is the reference product: whatever it needs, the framework has to support properly rather than by special case.
$ kiso resume restored session 8f2a from seq 412 pending write to src/billing.ts waiting approve this write? [y/n]
Kill it at any point. The next resume picks up the same pending approval.
npm i -g @vincemakes/kiso-code
A desktop version, eventually.
The idea is to give the same durability to work that is not only code, with one agent staying responsible for a project instead of a chat you have to keep rereading. It is early. Leave an address and you will hear once, when there is something real to try.
What should kiso take on in billing-api?
State is on disk. Close the window whenever.
A concept, not a build. Nothing here is running yet.
One email, when there is something to open. Nothing else.