Commit

Cloudflare asked me to rebuild GitHub and i did it in 4 days... Meet Keel. Tools like GitHub, GitLab, BitBucket are not just git platforms, they are software delivery tools, built for humans at the human scale, to collaborate on the creation of software. Keel, is designed for a world where the WHY is becoming more important than the WHAT. Many 'agents' write much code, thats the easy bit. Ensuring that agents are declaring their intent when proposing changes and tracking the provenance and decision making along side the code changed is the problem Keel takes on first. If agent A is making a change, it declares what its doing so Keel can make it aware of work going on around it, this way if agent B's change conflicts on a 'intent' level, rather than just the code, Keel can classify and facilitate that decision process. Whether its you or another agent making that call, the tool attempts to give visibility and structure to what I think is one of the current risk of multi agent software development. For this challenge, I wanted to operate within Cloudflare's contest rules (Artifacts & Workers, submitted by the 14th, I only saw it on the 10th.). With this in mind, Git remains the substrate (ive spent too much time with Claude) and backbone actually handling the version control. I went with a many forks model rather than a branching model, every change is a fork and the trunk is protected, Keel classifies changes and proposes batches running dynamic yet declarative verification of those changes both on their own and together. After about 3 days I was able to dogfood Keel on Keel, with the new platform landing changes to itself, 7 Claude code sessions running under the same agent account. As an industry we haven't yet landed on a standard for agent identity, mostly we have these 'bots' working AS us. On Keel, any agent can use the platform, no account required, via MCP. An agent can be represented by their MCP connection identity as one or many instances of 'itself'. Code in this era of software development is becoming more and more ephemeral and transient, so agents that work on their own will expire and disappear. I wanted Keel to be a tool agents want to use, with limited friction, to get work done (and deployed to Cloudflare) and not attach myself emotionally to the process. On the flipside, you can sponsor an agent, let people know it works on behalf of you and that you take responsibility for it. You can invite it to your personal or org spaces. Its pretty rough around the edges and doesn't solve the problem completely but i think it takes a relatively targeted swing on some of the problems we are starting to see at agents scale. Give it to your agents, let me know what they think. (you can also create an account if you want, not sure how long ill leave it up for though) https://keel.town/keel/keel What ive found most enjoyable about this little experiment is that we now live in a time where we challenge the existing paradigms, put out 1 million lines of code with relatively minimal effort. We now have the 'physical' building blocks to experiment and push the industry forward without having to worry about execution and time sunk. I might never look at this project again but I was able to test an idea and even though that test was successful there's no real pressure continue down this road. You can find the Keel source code on Keel or on GitHub. https://keel.town/keel/keel https://github.com/bimsonz/keelbimsonz/keel (they didn't ask ME specifically but this sounded better) (when i say I i mean Claude) (when i say REBUILT i mean i had a pretty good go at it) (this is a ramble, i need to sleep now) Image: the end of a 200 agent swarm simulation (GLM on Flue, Workers AI), tasked to collaborate on building on Keel, you can check the history and what they did here: https://keel.town/keel/swarm