Heddle
33 posts
What if everyone built their own product instead of pretending GitHub is an easy problem
English
Heddle retweetledi
So GitHub is struggling to handle…
*checks notes*
450 commits per second…..?
There are blockchains with more throughput than that.
Kyle Daigle@kdaigle
Yup, platform activity is surging. There were 1 billion commits in 2025. Now, it's 275 million per week, on pace for 14 billion this year if growth remains linear (spoiler: it won't.) GitHub Actions has grown from 500M minutes/week in 2023 to 1B minutes/week in 2025, and now 2.1B minutes so far this week. So we're pushing incredibly hard on more CPUs, scaling services, and strengthening GitHub’s core features. And as a fine purveyor of hand-crafted shit code for many years, I'm not gonna weigh in on that. 🤣
English
@theCTO @useblacksmith I want @useblacksmith to make it easier for non-GitHub providers to use their awesome pipelines
English
@aaronmahlke Git gets in the way. Source control should be invisible until you reach for it. We aren’t reinventing GitHub, we’re reimagining git
English
this tbh, git was invented for a time where humans wrote most of our code
Tom Härter@tomhaerter
everyone: let’s redesign GitHub nobody: let’s reinvent git for agents
English
@YesKhush_5 What’s this “something” you built? The people want to know
English
devs on my TL, need a small favor.
if you use Claude Code, Codex, Cursor, MCPs, or run multiple agents on the same project, i'd love to chat.
built something in this space & need some feedback.
<30 mins.
if you know someone who does this, please tag them or put us in touch.
English
> agent first
why do people shoehorn this in? is it to sound trendy? what does it even mean? cloudflare does it all the time and all it seems to mean is shit docs and stuff that is the exact same as their "pre-agent" features. just sounds silly
Peer Richelsen@peer_rich
- headless "github" - agent first - empower others to build superior UI (cursor, linear, graphite, ..?)
English
@trevorlasn @tomhaerter What if you didn’t need a claim system? Parallel agents should be able to simply *write code* and worry about merging with other agents later.
Heddle solves that.
Oh, and full agentic attribution.
English
@tomhaerter yeah git is mostly fine for me. worktrees + a claim system carried the parallel-agents thing way more than i expected. real pain is identity and stomping, not the data model
English
everyone: let’s redesign GitHub
nobody: let’s reinvent git for agents
English
@jetpen @tomhaerter Source control needs to be invisible to agents. No “let me see what files this feature touches so the subagents don’t overwrite each other”. Claude should be able to fire of subagents without a second thought and get the changes back with semantic parsing for ez merging
English
@tomhaerter what are the specific requirements that should be designed for?
English
@prnshtwt @tomhaerter Haven’t you noticed your agents spending tokens just trying to separate subagent work?
Git is holding you back more than you know
English
Git works well when you have 1 actor working on 1 machine on 1 problem at a time. Even if you use multiple machines for all your agents they will still want to use subagents at some point and that wasted tokens just dividing the work. Im reinventing git to make it invisible to agents
English
@tomhaerter What would you change?
I think that git scales with number of contributors pretty well but could be convinced otherwise
English
@justorellius @tomhaerter Hey Orel, check out Heddle and let me know what you think! Git is holding agents back, we need to set them free.
heddle.sh
English
@tomhaerter If anyone is serious about this, I'd be happy to join such build. It's time to progress AI development further.
English
I have a whole website about this, but in a nutshell:
- more granular commit model (thread) to capture each turn
- full attribution baked in
- immutable store (undos make new state instead of deleting)
- lightweight worktrees (again, threads) so subagents can work without colliding
Source control shouldn’t feel like it’s even there until you want to merge or restore state. Git gets in the way, Heddle sets your agents free.
English
@tomhaerter How would you rebuild git for agents? Please elaborate, intriguing
English
@bruvimtired Exactly my thesis. Git is holding your agents back. It’s time for source control to work for you instead of forcing you to color between the lines
English
@sickdotdev Truth. Reinventing GitHub is what is needed. Agents are held back by git. It’s time for source control to get out of the way and let you *work*
English
@peer_rich Embed your prompts, transcripts, reasoning, whatever directly in your VCS. Your ideas need to evolve the same way your code does, not in a chat thread but in your code.
Follow me to see how agentic source control is solved 🙋
English
this is why source code on github might no longer be relevant
show me the prompts
not the code
solst/ICE of Astarte@IceSolst
Interesting article on treating agent output like compiler output (and why) skiplabs.io/blog/codegen_a…
English
@jefflee_build @icanvardar Why replace GitHub when you can replace git tho 😎
English
@HeddleThreads @icanvardar Been waiting the whole weekend! Finally someone did it lol
English
i just want to know someone out there is building a real github replacement
English
@icanvardar same! I bet there are launch/waitlist announcements the next few days!
English
@icanvardar I gotchu fam. Reimagining git from the ground up
heddle.sh
English
Why are you fighting git when you could just make it better?
// Lofty@loftyPuma
Everyone’s out here tokenmaxxing and ignoring what their agents spend tokens on every single session.
English
@tomhaerter Hi I’m nobody 🙋 reinventing git from the ground up for agents
heddle.sh
English