3 ms·
> This happens constantly when multiple AI agents work on the same codebase What? Is the idea of "multiple agents" of flesh and blood writing code that far fe
by alkonaut 8mo ago
> This happens constantly when multiple AI agents work on the same codebase
What?
Is the idea of "multiple agents" of flesh and blood writing code that far fetched now?
- rs545837 8mo agoI meant when they each work on a separate branch and merge back, you get the similar kinds of conflicts, where a bunch of them should not even be a conflict, so weave is trying to solve it.
- alkonaut 8mo agoI still don't understand how it makes a difference if the agent is a human or a bot?
- vidarh 8mo agoThere's no fundamental difference, but in practice the difference is one of frequency. E.g. I sometimes have 10+ agents kicking off changes to the same small project at the same time, and likely to all want to merge within the next 15-30 minutes. At that rate, merge conflicts happens very frequently. The agents can mostly resolve them themselves, but it wastes tokens, and time.
- rs545837 8mo agoThis is exactly the use case, thanks for explaining.