> We initially built an integrator role for quality control and conflict resolution, but found it created more bottlenecks than it solved

Of course it creates bottlenecks, since code quality takes time and people don’t get it right on the first try when the changes are complex. I could also be faster if I pushed directly to prod!

Don’t get me wrong. I use these tools, and I can see the productivity gains. But I also believe the only way to achieve the results they show is to sacrifice quality, because no software engineer can review the changes at the same speed the agent generates code. They may solve that problem, or maybe the industry will change so only output and LOC matter, but until then I will keep cursing the agent until I get the result I want.

It’s fascinating that many of the issues they faced I’ve seen in human software engineering teams.

Things like integration creating bottlenecks or a lack of consistent top down direction leading to small risk adverse changes instead of bold redesigns. All things I’ve seen before.

Weird twist the hiring call at the end for a company that says

> Our mission is to automate coding

I'm very curious about how much of it is re-using (remixing?) an existing browser implementation it has seen in the while or its trained on. Even in that case, 99% of all code isn't doing anything novel so this copying would still have significant practical use.

There's a clear conflict between SKILLS, tools and multi-tasking.

I think "intra-context" tooling is already dead. It's too narrow.

It's all "extra-context" now: how one instruments for multiple agents, at multiple times, handling things.

Personally, I think the best tool in this realm will come from open source, and be agnostic (many agents from many places interacting), in order to leverage differences between subtle provider qualities (speed, price and so on).

Building a browser is an interesting and expensive experiment. How much did it cost?

All of these things have readily available analogues on the web which means they are more than likely just laundering open source code & claiming victory.

Slightly off topic, but they want to move from solid to react? Isn't that the reverse of the newest trend? Would be interesting to know more.

Over the past year or so, I've built my own system of agents that behaves almost exactly like this. I can describe what I'd like built before I go to bed and have a fantastic foundation in place by the next day. For simpler projects, they'll be complete. Because of the reviews, the code continually improves until the agents are satisfied. I'm impressed every time.

I would love to know the cost of building this browser. I think that multi-agent orchestration systems will probably be the theme for systems this year.

I think the north-star metric for a multi-agent orchestrator system would be how much did it cost to get this done. how much better could we have done? should we have used a cheaper model for doing a trivial task and an expensive one to monitor it?