@thorstenball: Why are you still using pull requests? Is it for code review? If so, do you really think your or your colleagues catch …

Why are you still using pull requests? Is it for code review? If so, do you really think your or your colleagues catch bugs and mistakes that an Opus 5.5 or Fable or Astra won't find? You can literally spawn all three of them and have them check four times each. (Also, don't tell me you don't have a "stamp plz" Slack channel or group chat somewhere.) Is it for knowledge sharing? Surely there's better ways for that now than the PR, no? We have models that can generate explainer videos, presentations, podcasts, games, quizzes, walkthroughs, ... for any piece of code it can reach. Is CI the reason? Well ackshually, CI means continuous integration and its original meaning is the *opposite* of having long-lived branches and PRs. But, leaving that aside, your agents are hopefully already running the tests before they push something, and hopefully they can run as long as they want and don't block you so they can run the whole test suite and generate "irrefutable proof" and end-to-end demo videos and so on... And so they run the tests and confirm and then you push to a branch and everything runs again and then you merge and then it runs again? That doesn't make sense, does it? Maybe you work in open source and you accept contributions, in which case I can't speak to the value of pull requests. It's been 2 years since my last OSS contribution. But from what I heard, the time of the PR is coming to an end in OSS too? I honestly don't get why people still stick to PRs. With agents you can now move 10x faster, you can finally do real continuous integration, and get more confidence in the changes the agent made. Don't slow yourself down by having all the changes pile up in a PR.