Code worth signing.
Joined May 2026
- Tweets 113
- Following 97
- Followers 18
- Likes 215
1 Photos and videos
Move over Grit, sley is slaying
Git: lighter, faster, and smaller đź‘€
heddle.sh/blog/sley-vs-git
1
1
42
Jun 15
Heddle needed a better embedded git implementation, so I built it.
Very promising so far, it doesn’t just beat other libraries, it’s beating git 🔥🔥
Jun 15
maybe rebuilding Git from scratch wasn't such a bad idea after all đź‘€
ALT Chart comparing Git and Sley write-path command timings on small, medium, and large repo clones. Bars show median milliseconds for hash-object -w, write-tree, update-index --refresh, add -u, add one file, and commit-tree. Sley is faster on most commands with complete git-test parity in those areas.
1
1
52
Heddle retweeted
Jun 15
maybe rebuilding Git from scratch wasn't such a bad idea after all đź‘€
ALT Chart comparing Git and Sley write-path command timings on small, medium, and large repo clones. Bars show median milliseconds for hash-object -w, write-tree, update-index --refresh, add -u, add one file, and commit-tree. Sley is faster on most commands with complete git-test parity in those areas.
1
2
98
Heddle retweeted
Jun 13
Hey Dax! I’m building vcs for agents first. I think this is right up your alley, it is the lib first and harness agnostic.
Primary features for OpenCode:
- threads (worktrees but good)
- atomic undo/redo (agents can rewind to a given tool call or fork from a prior state or whatever)
- agentic attribution (know who delegated what to what agent)
- anti-drift knowledge (critical context embedded in the codebase and injected into the harness on read, it even uses semantic parsing to follow moved/renamed funcs)
heddle.sh
1
1
4
562
Heddle retweeted
Jun 13
New life goal. Build something so good that a world superpower calls dibs.
Jun 13
The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees.
The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance.
Access to all other Claude models is not affected.
We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible.
Read our full statement: anthropic.com/news/fable-myt…
1
1
46
Heddle retweeted
Jun 12
I gotchu.
Heddle is vcs built on tasks instead of commits. It gives agents a “capture” command and lets them fork and experiment and preserves all of that information.
Happy side-effect, a squash merge can be lossless! Git forces you to pick between a navigable history and a complete history, all we needed was a more granular commit command.
1
1
224
Heddle retweeted
Jun 12
Imagine how good GitHub would be if their incident reports looked like this
Our deepest apologies for the downtime today between 13:17 and 14:18 UTC. Tens of thousands of businesses trust Polar with their billing, and an incident like this should not happen. We'll publish a full post-mortem in the coming days and take actions to make sure it does not happen again. In the meantime, here's exactly what happened.
We rotate secrets frequently as a security policy. Today we rotated our database credentials – but a flaw in our config, where the credentials were tied to the database's Terraform resource, caused Terraform to trigger a full resource replacement. Our production database was replaced. It took us an hour to restore and bring everything back.
Was any data lost? No. We run point-in-time recovery with remote backups, hosted on Render with enterprise support. We immediately began a PIT recovery, replaying WAL up to the moment before the Terraform change applied. Recovery completed at 14:16 UTC; we confirmed full data integrity and brought infrastructure back online at 14:18 UTC.
A few edge cases we're reconciling now – none involve lost data:
— Our API stayed up for ~50s after the latest point in time recovery point and kept accepting event ingestion (which we double-write into Tinybird). A few hundred events landed there; we're going to replay them.
— We received 3 Stripe webhooks for in-flight transactions as we went down. We're resolving these and reaching out to the affected customers directly.
— After restore, our webhook worker was properly restarted to point to the recovered database. That's fixed; it's catching up now, so webhook delivery is delayed but recovering.
Polar is fully operational. The only residual effect was delayed webhook delivery while the worker catched up, which it has now. No action is required on your end.
Our post-mortem will detail the full timeline and the guardrails we're adding so this class of failure can't recur, and we’re truly sorry it happened in the first place.
2
7
2,090
Jun 11
Worktrees are brittle and require careful scripting and care. If you’ve figured them out, more power to you.
Heddle brings you threads. All the power of a worktree with none of the headache.
Jun 10
Am I the only one who thinks git worktrees are fucking confusing?
1
1
1
50
Jun 11
A thread is a lightweight isolated view of your repo. It’s copy-on-write when your filesystem supports it and can automatically include your .gitignore files for you.
Threads exist to isolate agent work, every agent and sub agent can have their own.
1
13
Heddle retweeted
Jun 8
@jh3yy is going on css side quests at this point. He must be bored.
What’s something you wish you could do on the web that just doesn’t feel possible?
I’ll start. We’ve got Liquid Glass, I want to see paper so realistic you feel like you can touch it.
Tactile Texture? Solid Elements?
Liquid Glass is neat, that texture would just be that 🧑‍🍳💋 that takes a page design from 👀 to 🔥
1
1
30
Heddle retweeted
Jun 6
Claude Design was struggling to get what I wanted and my wife remembered how @AnthropicAI said you need to encourage Claude to get good results.
So I told it to take a break, breathe, and try again. Can you guess which is before and after?
1
1
31
Heddle retweeted
Jun 6
Anything from a reasoning note to your entire chat can be stored. But it needs to fit nicely into your agents context so less is more imo.
1
1
24
Heddle retweeted
Jun 6
When you go to review your code, that stale knowledge should be surfaced for you right in your review, not a separate system to update.
1
1
1
27
Heddle retweeted
Jun 6
Everyone is trying to find ways to host memory beside their code. md libraries, knowledge graphs, vector dbs, you name it someone’s made a startup for it.
All of that invites drift. You need knowledge attached semantically to your code so when the code is modified, the knowledge is automatically injected in your agent’s context.
2
1
1
48
Jun 5
Have you ever had a situation where you have your public repo but need a specific commit to remain private?
Heddle’s core allows exactly that.
Visibility isn’t constrained to the repo level anymore, and in the age of AI that’s more important than ever. No one wants to broadcast a security fix before their users can adopt it, that’s the reason behind half the zero-days we’ve seen recently.
1
2
43
Jun 4
AI coding isn’t becoming one agent writing code. It’s becoming many agents trying, comparing, landing, and leaving behind provenance.
Jun 4
@theo đź‘€ I think you've been looking for this
âś… CoW worktrees
âś… context embedded in the repo
âś… full agentic attribution
... and more 🔥
see more at heddle.sh and checkout the github to install and try it today
3
1
2
126