I find this to be a bizarre sentiment. It’s an artifact that exists. The chances of me making this by hand are 0. This would be a full time job for 3 years to research and build this. For 10 people. And it would have to charge a ton of money to access in that case.

> This would be a full time job for 3 years to research and build this. For 10 people.

No it wouldn't.

Look at the commit history. I’ve been working on this essentially every single day for over a month.

Thank you, I was scrolling and scrolling in utter disbelief. It sounds absolutely dreadful. Would drive me nuts to listen to for more than a minute.

I really think git worktrees are a bad approach. You’re better off in my view with one shared state and dealing with conflicts live by dividing tasks ahead of time using beads and letting agents communicate with each other using Agent Mail and file reservations.

I’ve been able to productively run 12+ agents from CC, Codex, Gemini-cli at the same time this way and it works really well.

That's a pretty interesting approach, would love to see a demo of your setup :) my email is avi@superset.sh if you're down to chat!

I recorded this around a month ago, which is funny because it's already pretty obsolete since my tooling has advanced so much since then:

https://www.youtube.com/watch?v=68VVcqMEDrs

My full stack is detailed here on this site I made recently:

https://agent-flywheel.com/

Thanks, this is cool!

This sure looks similar to something I posted on X 2 weeks ago:

https://github.com/Dicklesworthstone/misc_coding_agent_tips_...

You be the judge:

https://x.com/doodlestein/status/2002423770259345451?s=46

I can't believe you're accusing someone of plagiarism because they had a similar idea that "claude code would be safer if it couldn't do destructive git calls". They also added much more protection, implemented it as a plugin, wrote thorough docs and have shipped many updates since.

You wrote a markdown file. Shut up.

My analysis: https://x.com/theo/status/2006474140082122755

lol, was wondering why I didn’t see your brain dead reply, and it’s because I’ve had you muted for years.

Wow this readme reads so similar it rather unlikely a coincidence?

Yeah, I was being polite. This is outright plagiarism. @dang

"License: This repository contains documentation and configuration files. Use freely for personal or commercial projects."

You really think that's the same as someone blatantly plagiarizing the work and passing it off as their own? Give me a break. This is dishonest and odious.

"Someone" is a big assumption these days. What if it was an AI agent just poking in its own source code?

Its not about what I think, thats what the license says.

OK thanks for your input.

Definitely too similar to be a coincidence

Sure does.

I did something similar except mine is fully open source and works way better:

https://github.com/Dicklesworthstone/ees

I had a striking realization recently that has helped me improve my project. What matters isn’t what I think, it’s what the users which actually use the system think. Which is sort of obvious but somehow less so when the users are AI agents…

“You’re so right and those tools look really good.”

Is there value is this considering how they’re trained to be agreeable and have no real reasoning or proper discernment?

If the tool sucked, they would not be saying that. I’ve tried. Also they did give some negative feedback and it has already been used to improve the system.

It actually does work well. And perhaps it’s not even that surprising that it would work, because we know that’s what works already for human developers and companies, so we have an existence proof already.

I was recently explaining to someone how Barra risk factor models work and how they’re used by hedge funds to measure whether someone actually has investing skill or just “got lucky” (among many other use cases). And I realized that it would make an interesting article. So enjoy!

This sounds like it would be a good underpinning for a decentralized blockchain file storage system with its focus on immutability and redundancy.

But a blockchain is already immutable. It becomes decentralised and redundant if you have multiple nodes sharing blocks.

No need for an underpinning, it is the underpinning.

if you're storing the blocks in one place, its not decentralised.

The metadata would be crucial for performance, and given that I assume you'll want a full chain of history for every file, your metadata table will get progressively bigger every time you do any kind of metadata operation.

Plus you can only have one person write metadata at one time, so you're gonna get huge top of line blocking.

And yet no one needed a blockchain to implement this.