It's fascinating to see new UI primitives and concepts get invented in the LLM era. The sea of creativity makes it hard to even understand most of what each new app does, and nobody describes them well. When I went to the Hermes agent web page, I was left with zero clue about what it did or what it could do. It took a bit of digging to find the right part of the qm page that helped me grok what was going on.

I've become attached to Orca (yc-backed) for managing coding sessions in the past week, but some sort of postgres session db is what's really lacking. So, maybe it's time to try qm.

Love seeing this direction along with Buzz.

The hardest problem in multiplayer agents, at least for us, has not been the agent loop. It is scoping and QM's per-person scopes plus shared rooms is a sane answer for a company-wide assistant.

I build in the adjacent lane, AQ (aq.dev), a multiplayer coding harness where teams run Claude Code and Codex together), so seeing YC ship "a multiplayer agent harness for work" is validating and a little surreal.

Is Hermes the best openclaw like agent as they mention running it before?

Also, what are power uses really using openclaw like systems for?

What is yc software?

Interesting to see they shipped an "anti-slop" taste skill:

> description: Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

> - *PREMIUM-CONSUMER PALETTE BAN (mandatory, second-most-recurring AI-tell):* - For premium-consumer briefs (cookware, wellness, artisan, luxury, heritage craft, DTC home goods, etc.)... - Backgrounds: `#f5f1ea`, `#f7f5f1`...

> Landing pages and portfolios are *visual products*. Text-only pages with fake-screenshot divs are slop.

https://github.com/yc-software/qm/blob/7f2c916360f1797a8ff2a...

looks like an internal tool that yc rushed out the door to minimize any most lost ground to Buzz. That said, I'd be curious what folks think comparing these two tools.

it says "Each deployment runs in the operator's own cloud account"

But feels like its written to run on one mac/vm and carries same drawbacks of other similar platforms. I'd rather use Hermes/Openclaw for oss or closed managed agents like Tasklet or Prajvis

> We take contributions as human-written text, not code — see CONTRIBUTING.md. Describe the change you'd like informally in a .txt or .md file in adrs/, and if we're aligned we'll handle the implementation.

Interesting approach to open source contributions. Closer to feature requests at that point?

i find something a bit funny in an ai project, written by ai, requiring human-written text with specific guidance to not use ai.

"Given that coding agents write most underlying code now, we'd prefer PRs in the form of human-written text. [...] Please do not have AI artificially expand what you'd like to do into a formal proposal."

>We take contributions as human-written text, not code — see CONTRIBUTING.md. Describe the change you'd like informally in a .txt or .md file in adrs/, and if we're aligned we'll handle the implementation. Report vulnerabilities privately — see SECURITY.md, not a public issue.

Starting to think people were right when they talked about our industry itself having an AI psychosis problem.

Other than the hosting providers, who has made money directly from running OpenClaw in constant loops?

This software appears to be yet another solution in search of a problem designed to burn as many tokens as possible.

Sweet, now YC itself will be the startup :D.