Live data from Hacker News

qm – Multiplayer agent harness for work

github.com

31–40 of 186 posts

Re: qm – Multiplayer agent harness for work

#31

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. "

XY problem, don't expand the design doc before you have the idea for the design. Don't compile down into lower abstraction levels until necessary

Re: qm – Multiplayer agent harness for work

#32
post #24
post #2

>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.

As someone who has maintained an open source project, I much prefer written bug reports and feature requests to drive-by PRs. (I almost don't even care if they are LLM-written.)

I appreciate open source maintainers and understand that it's a lot of thankless work, and I know what I'm about to say comes off as (and probably is) ignorant but the hoops projects make me jump through to report hugs or security issues is often like working for corporate in terms of bureaucracy and a lot of times I just don't bother. I've reported a few dozen bugs so I'm not prolific here but also not speaking without any experience at all. And then you often have automation (eg. Debian) closing bugs because nobody looked at it and saying to reopen it if it's still a problem in the current release.

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.

Re: qm – Multiplayer agent harness for work

#34
post #24
post #2

>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.

As someone who has maintained an open source project, I much prefer written bug reports and feature requests to drive-by PRs. (I almost don't even care if they are LLM-written.)

I sometimes add a PR with the fix for a bug report I make, but the last few have been ignored in favor of the maintainer's own code. So I think I'll stop doing PRs and just point to code lines instead.

Re: qm – Multiplayer agent harness for work

#35
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.

Re: qm – Multiplayer agent harness for work

#36
post #4

Is Hermes the best openclaw like agent as they mention running it before? Also, what are power uses really using openclaw like systems for?

Still figuring it out, but it's been really convenient to have an always-on agent that has access to internal systems and can be triggered by webhooks. Some examples of what we use it for: - 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 quest…

I think the interesting challenge isn’t running agents, it’s reviewing their work. The more code agents produce, the more important provenance, review ergonomics, and trust become. I also suspect repository platforms will need to evolve there over the next few years.

Re: qm – Multiplayer agent harness for work

#37
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.

Re: qm – Multiplayer agent harness for work

#38
post #29

Earlier quoted context omitted.

Someone from Y Combinator made some software. Must there be narrativization of everything?

Yes, please! I'd like to know more, for example why now?

At least for me, I often have a hard time believing people’s stated reasons for whatever they’re doing.

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.

Re: qm – Multiplayer agent harness for work

#39

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. "

Yet the README is generated ("Two skills maintain the boundary in both directions.") and the demo is .. a Mobius strip?

I'd prefer if you explain what it is you are building in the form of human-written text.

Re: qm – Multiplayer agent harness for work

#40

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 bec…

AI needs entirely new primitives in many areas.
Post reply on HN