As usual I did not do what I planned to do. Instead I fell for another tunnel of technical rabbit hole; Read some drama that was going on with open source AI CLI assistant(weird to find out there is drama in this space and that I am not even far from it); I went splunking through the web for a haskell blog and found a completely seperate person he replied to about the article that I was trying to find; I rediscovered an old lecture I never finished watching that happens to somehow relate to all of this; I discovered an amazing person doing animations with ableton and strudel.
Drama on the Command Line
Oh my gosh that was a lot! Let's unwrap that by breaking down some of those details. The open source drama was something that I actually discovered the day before yesterday. Apparently there is a word for that 'ereyesterday' nice to know. Will never use that. Back to the drama, the subject is open code and Crush. Two open source AI Agent CLI tools that are all the rage these days. Here is what I could some up from the situation after reading the two tweets (I did not look at replies because I don't have a twitter account): So here’s what I managed to piece together from a late-night chat I had with someone named boshy. Open Code was built by three devs. Then one of them, Kujtim, sold the repo to Charm (the Bubble Tea people). That wouldn’t be a big deal, except, according to the other two devs, they didn’t agree to the sale. On top of that, they say their contributions got wiped from the Git history after the repo was transferred, and Charm rebranded the whole thing without properly crediting them. So the remaining two devs remade the project from scratch under a new org called SST.
Charm responded saying it was all legit. Kujtim had built the original repo using Charm’s stack, and the project was transferred fair and square. Boshy mentioned some screenshots and posts from both sides, but things still feel murky. At one point we were talking about whether it’s even possible for someone to rewrite Git history like that without leaving traces. Spoiler: it’s not easy to cover your tracks if you know where to look. In the end, we both agreed that this seems less like a malicious takeover and more like a mess of poor communication, ego, and clashing expectations.
Still, it left a bit of a sour taste. Open source projects live and die by trust, and this one hit a weird nerve for people. Anyway, I was supposed to dig deeper into it today but, true to form, I didn’t.
TL;DR turns out 1. I am late to it, it apparently happened last month and it was announced on twitter. 2. Some of the claims should be easy to verify with git, yet did not seem to be verified by either poster which is weird. 3. I said I would take a closer look at the drama today and I did not take that look. That wraps this segement folks! On to the next waste of time for my day.