4 ms·
Does this actually matter for multi-agent use cases? Surely people that are using swarms of AI agents to write code are just letting them resolve merge conflict
by deckar01 7mo ago
Does this actually matter for multi-agent use cases? Surely people that are using swarms of AI agents to write code are just letting them resolve merge conflicts.
- rs545837 7mo agoSo that you don't feel that I am biased about my thing but just giving more context that it's not just me, its actually people saying on twitter how often the merging breaks when you are running production level code and often merging different branches. https://x.com/agent_wrapper/status/2026937132649247118 https://x.com/agent_wrapper/status/2026937132649247118 https://x.com/omega_memory/status/2028844143867228241 https://x.com/omega_memory/status/2028844143867228241 https://x.com/vincentmvdm/status/2027027874134343717 https://x.com/vincentmvdm/status/2027027874134343717
- deckar01 7mo agoThose users all work for companies that sell AI tools. And the first one literally says they let AI fix merge conflicts. The second one is in a thread advocating for 0 code review (which this can’t guarantee) (and also ew). The third is also saying to just have another bot handle merging.
- rs545837 7mo agoThanks a lot for the fair criticism, Appreciate it! You're right that those links aren't the strongest evidence. The real argument isn't "people are complaining on twitter." It's just much simpler when two agents add different functions to the same file, where git creates a conflict that doesn't need to exist. Weave just knows they're separate entities and merges cleanly. Whether you let AI resolve the false conflict or avoid it entirely is a design choice, we think avoiding it is better.
- deckar01 7mo agoDear god, it’s bots all the way down.
- rs545837 7mo agoWhat do you mean?
- deckar01 7mo agoIt’s your GitHub profile. It looks suspiciously just like the other 10 GitHub users that have been spamming AI generated issues and PRs for the last 2 weeks. They always go quiet eventually. I suspect because they are violating GitHub’s ToS, but maybe they just run out of free tokens.
- rs545837 7mo agoThanks again for criticising, so tackling each of your comment: GitHub’s ToS, because you suspect, so I can help you understand them. > What violates it: 1. Automated Bulk issues/PRs, that we don't own 2. Fake Stars or Engagement Farming 3. Using Bot Accounts. We own the repo, there's not even a single fake star, I don't even know how to create a bot account lol. > Scenario when we run out of free tokens. Open AI and Anthropic have been sponsoring my company with credits, because I am trying to architect new software post agi world, so if I run out I will ask them for more tokens.
- deckar01 7mo agoAnd you are opening issues on projects trying to get them to adopt your product. Seems like spam to me. How much are you willing to spend maintaining this project if those free tokens go away?
- rs545837 7mo agoWhen you're just a normal guy genuinely trying to build something great and there's nobody who believes in you yet, the only thing you can do is go to projects you admire and ask "would this help you?" Patrick Collison did the same thing early on, literally taking people's laptops to install Stripe.
- vidarh 7mo agoI'm running agents doing merges right now, and yes and no. They can resolve merges, but it often takes multiple extra rounds. If you can avoid that more often it will definitely save both time and money.
- rs545837 7mo agoThanks for the great explaination again.