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.
Also, what are power uses really using openclaw like systems for?
Yesterday I just decided to try writing my own version (100% just for me, not open source, no monetization plan, incredibly custom) and I've been enjoying working on it so far (I know, I know, it's been a day, honeymoon period and all that).
Part of it is I like building software (even if I'm not writing every line) and part is I like having full control. Turns out (and many people have said this) the basic agent loop really isn't all that special. There are a million levers to pull and what not outside the base loop but that the fun part for me. Trying out different ways to add on to the core concept.
I'm really enjoying being untethered for things like "how will I monetize?" or "how do I make this generic so others can use it?". If I need functionality I just add it in, I don't need to make it infinitely pluggable, etc.
All that said, I'm thankful to things like nanoclaw and then Hermes for exposing me to the core ideas. I just want to put my own spin on it.
- automatically fixing simple CI failures
- getting production alerts and automatically creating RCAs and a fix PR
- periodically checking slow DB queries and finding ways to speed them up.
- creating charts to answer one-off questions about our data
I've tried using it as an on-the-go coding agent as well, but found I prefer more interactive agents, so I can see what the code looks like.
I have one reading my second tier RSS feeds and newsletters and giving me news/market updates filtered for things important to me
Oh grand. The world will be full of agents talking to agents and nothing getting done. So pretty much the same only I can just leave my machine awake to look busy.
> 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...
I'd like to know more, for example why now?
The substance <> narrative relationship is backwards a lot of the time. Someone does something for a nebulous multitude of reasons, and then post-hoc fits their decision-making into a logical explanation that sounds nice.
There is some psychology research supporting this as well.
I suppose if you see the narrative itself as part of the release, that might be interesting. But most of the time I’d rather just hear plainly and straightforwardly what the thing is.
Or at the very least, I am very accepting of releases which do not include rationalization / narrativization and don’t think it’s required to include.
Interesting approach to open source contributions. Closer to feature requests at that point?
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
"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."
0: https://github.com/pjlsergeant/byre?tab=contributing-ov-file
I'd prefer if you explain what it is you are building in the form of human-written text.
I personally would probably have the readme generated based on that directory as the primary document, probably with another `readme_generation_rules.md` in the ADRs directory, and I would be pretty ruthless about disallowing all the slop-adjacent wording.
Starting to think people were right when they talked about our industry itself having an AI psychosis problem.
Like I said, I do understand and appreciate how annoying it must be. But there are two ways to look at this, one is that it's free software a bug report is like a support request - and of course nobody should expect free support. The other way to look at it is that by reporting bugs I'm volunteering as QA for the project and the report is beneficial.
> the project does not accept patches from random people on the internet
https://sqlite.org/copyright.html
In their case, it's motivated by a desire to keep copyrighted code out of the SQLite implementation, but I'm sure it has a nice benefit of making it so that an extremely widely used project doesn't get drive by, low effort code review requests while still allowing the community to engage.
Asking that "random people on the internet" don't sent code is not altogether a novel, post-AI idea.
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.
I've been playing around with using a hidden markov model informed by a UI state event stream, with the end state fed into the Agent as a hint on each message turn. Then the Agent can make a tool call to add events to the HMM. This has been really interesting, but I haven't struck the right balance to make it actually feel good for the user yet