Why Kelson exists
Every engineer runs agents alone. The team has no shared room for the work and no shared memory of what those agents learned. Coordination disappears into private sessions just when it matters most.
Manifesto
The project needs a room of its own.
Kelson is the shared coordination layer where engineering teams and their AI agents build in the same visible, remembered place.
What Kelson is
The canvas is where the team plans together. Runs are shared agent sessions anyone can watch, checkpoint, steer, or hand off through the conn. The playbook is one project memory that every run loads.
Why now
Agents collaborating directly with agents still fail at coordination, as CooperBench 2026 makes visible. Coordination is a human skill, so the coordination layer must be human-structured.
Where this goes
Kelson grows org-wide: local coding agents streaming into one record, approvals routed to the right owners, and a project that remembers everything even as its people and tools change.
The name
A kelson is the beam that binds a ship’s frame to its keel. People rotate, agents change, and the project stays one thing.