Watch kaos-control build something from nothing

One week since launch. The demo is up. Watch closely at the end.

May 19, 2026

A closed dark-grey laptop on a warm walnut desk in late-afternoon light, beside it an iPad showing a paused video frame with a single amber play-triangle centred.

I shipped kaos-control one week ago. Since then I have been pushing it to where one continuous take could capture it building something from nothing. That video is up now.

Sixteen minute video, 10 minutes of effort. The chapters walk through setting up a project, capturing an idea, finalising the requirements, planning and building, and then standing up DevOps pipelines for deployment. The thing it builds is a real website. If you read the launch piece and wondered whether the workflow actually holds together under load, the video is the show-don’t-tell.

What has released since the launch

One week of releases has also moved the product on. The agent work queue to load up work to keep the agents busy without burning all your tokens. Startup time is down from minutes to 76 milliseconds. The test suite is expanded and fully green. Priority and release are first-class fields now. The security review baseline (govulncheck, gosec, gitleaks) is in the lint pipeline. And so much more.

A craftsman’s workbench under warm tungsten workshop light. Precision tools are laid out in labelled wooden trays. A clear acrylic partition runs gently across the bench; on the far side, a single finished piece of carved walnut rests on a slip of paper-white card, watched by a small amber LED on the partition edge.

The Claude Enterprise unlock

If you work in a Claude Enterprise environment, you have probably hit this. Most agentic tooling needs Claude Code running with --dangerously-skip-permissions, and your administrators have, sensibly, switched that flag off. The default driver in kaos-control had the same problem.

The new claude-mediated driver is the answer. It runs Claude Code in default permission mode and routes every tool call through a PreToolUse hook for real-time allow/deny against a per-agent path allowlist and a bash command allowlist. Writes outside the allowed paths are denied by the hook before the tool call reaches the filesystem. Every decision lands in the audit trail. There is an observe-only mode so operators can preview the policy against real work before turning enforcement on.

The mediated driver is the surface; the agent sandbox underneath it is the deeper story. Allowlisted write paths, per-agent permission policy, lineage-scoped writes. Policy enforcement rather than aspirational restriction.

Get it, use it, talk

Get it on GitHub: github.com/kcsinclair/kaos-control. Single Go binary; the releases page has builds for the platform you are on. Point it at a project directory and the workflow walks itself.

For the shape of it before installing, kaos-control.io has the demo, overview, and roadmap.

If you are evaluating kaos-control for a Claude Enterprise rollout, or you have a harder agent-sandbox question, talk: tek42.io.

One last thing

A laptop on a wooden desk displaying a website with a video player at the top. Inside the player, the same desk and the same laptop appear at lower resolution, recursing several layers into warm amber haze.

The website I just sent you to was built by kaos-control during the recording you just watched. The demo embedded on the home page is the recording of the home page being built. The thing builds itself. The loop is closed.

Keith Sinclair

Discussion about this post

Ready for more?