Hekton
One human, several AI agents, and the architecture that holds them together. Explore the machinery and the labs, then read the build logs.
Enter the journalHover any node to inspect a part of the factory.
Hekton: A personal agentic engineering operating system. A factory for running multi-agent software projects with real structure.
The premise
Hekton is harness-agnostic and provider-agnostic by design: swap the coding agent, swap the model, route a job to a local model when that's the right call, and the factory doesn't change shape underneath you. What stays constant is a layer you're not meant to notice: taxonomy, contracts, and governance that apply to every agent equally and run on every change, without you having to remember to invoke them. The core doesn't write software by itself; it decides which lab or agent should, then holds the result to the same bar every time, no matter which harness or model did the work.
“The best leaders are those the people hardly know exist.”
Lao Tzu · Tao Te Ching
The invisible layer
Select an icon to see what it does.
The model
Every capability in the factory starts as a small, single-purpose gear that plugs into the core. Gears combine inside a lab, a bounded experiment proving one job is worth doing well. When a lab proves itself, it graduates: it transforms into a standalone public repo, a Transformer that works on its own or plugs straight back into Hekton.
01 · Gear
A single-purpose piece of the factory's machinery: a rule, a contract, a script.