They said from the beginning it was compute constraint and that OpenClaw was causing way more usage than they could handle

Well if you prompted the PR you know the context

"Who's the end user for this?" obviously people who use figma

It's just email man you do not need to throw an AI buzzword in front of everything

If you're building a standard app Opus is already good enough to build anything you want. I don't even know what you'd really need Mythos for.

You'd be surprised. With React, Claude can get twisted in knots mostly because React lends itself to a pile of spaghetti code.

What's an alternative library that doesn't turn large/complex frontend code into spaghetti code?

Vue (my favorite) and Svelte do well.

I've got a gfx device crash that only happens on switch. Not Xbox, ps4, steam, epic, or anything. Only switch.

Opus hasn't been able to fix it. I haven't been able to fix it. Maybe mythos can idk, but I'll be surprised.

Consumerism... if it ain't the best, some people don't want it.

Time/frustration

If it’s all slop, the smallest waste of time comes from the best thing on the market

Also 640 KB ram ought to be enough for everybody.

Opus sometimes makes poor long term decisions and really struggles with even mid size (~10k lines) existing codebases.

This is true if you know what you are doing and provide proper guidance. It’s not true if you just want to vibe the whole app.

You'd need Mythos to free your iPhone, SamsungTV, SmartWatches or such. Maybe even printer drivers.

i sincerely doubt mythos is capable of jailbreaking an iphone

Good luck trying to send emails during a LaLiga match I guess

If there was no service fee how would Ticketmaster generate any revenue?

Multi-year exclusive contracts paid for with cash advances.

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 think there’s other HN threads reporting multiple issues with it. Can’t remember which thread I read it but someone said it’s very hard to uninstall because agents will keep reinstalling it once it’s part of a project.

YMMV but this seems like a simpler port: https://github.com/Dicklesworthstone/beads_rust

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.

Not really any different to GitHub Actions