I tried Beads and it kept breaking in such frustratingly random ways that I just added a Linear MCP server and called it a day. That's really all you need.
I've been using Beads for 5 different projects, and Beads and/or Dolt failures have been a regular thing. It's own "doctor" feature is sort of disturbing, in that it (1) tells me that my Beads setups are always at least a little bit broken, but (2) can never fix all of the issues. Hopefully the 1.0 designation means that Steve is out of "throw shit at the wall" mode. Beads is fine as a replacement for Markdown files, but I'll never go near Gas Town because of my experience with it.
Agreed. I kinda concluded that the expected `doctor` usage is to have an agent run it for you and then they can try to figure it out when `doctor` can’t fix the issues.
I tried both Beads and Gas Town and had the same experience.
These fully vibe coded tools seem to have near zero QA. The fact that they ship with a `doctor` command that you regularly need to run (even if you didn’t change anything about your environment) tells you all you need to know.
This moat is rapidly disappearing though. Cloudflare is catching up, most apps (including TanStack Start) can be one-click deployed without configuration now.
Why should a low-powered Android phone be downloading and running a full Markdown parser or syntax highlighter? Stuff like that is obviously something that should be handled by the server and just returned as final HTML.
Yes, broadly. The main structural difference is that we’re agent-agnostic, so we can combine lab-native CLIs in one workflow. GitHub will likely struggle there because they have direct partnerships with Anthropic and OpenAI.
On the features themselves, we have a better UX across integrations, and more advanced features like video recording.
This seems like a weak argument. GitHub is already agent (not just model) agnostic, they have Copilot and Claude Code. I just don't see how this is a business, sorry.
reply