Durable state
Every Work item, session, decision, artifact and handoff is recorded as it happens. When an agent stops, the record of what it did — and why — remains.
System of record · Control plane
Keep using Codex, Claude, Gemini and your own internal agents. Kernel gives their work persistent state, clean handoffs, approvals, artifacts and human visibility across every runtime — without asking you to change the tools your agents already run.
Self-hosted and local-first. Your data and your agents' work stay in your deployment.
What Kernel is
Every Work item, session, decision, artifact and handoff is recorded as it happens. When an agent stops, the record of what it did — and why — remains.
Approvals, blockers and a single "Needs You" inbox put a person in the loop where it matters. Nothing irreversible happens without someone deciding it should.
Kernel is not another agent. It sits alongside the runtimes you already use and gives their work one shared structure, so a handoff between them keeps its context.
The handoff
Kernel compiles the goal, the constraints, what is already done, the decisions taken and the open questions into a compact package. A person can read it before anything starts, and the destination runtime begins with the context rather than the chat log.
The model
Tenant isolation, least-privilege tokens, a metadata-only default and no per-person ranking. Read the security and privacy architecture, or ask for access.