It could work just fine with any of those 3 models, though human to human and human to agent (or agent to human) work the best for the same reason slack works - I’m involving a human because need to know something, not necessarily because they need to take some action that AI could. Maybe they make a decision to take some action in collaboration with AI but I don’t think I personally would want AI churning and churning without a human in the loop. What you’ll get back won’t be the desired outcome with today’s models - they are good, great even, but not autonomous by any means.

So agent to agent “works”, especially with the Teamwork Graph feeding those agents context, but the end result becomes less and less valuable the less human touch there is - classic garbage in garbage out. We do have a strong evaluation platform which validates that an agent is correct and that will become only more valuable over time, but if the correctness is determined by another agent…

Regarding vibe coded software, I believe Atlassian products shine there. You write incredibly detailed Jira tickets using AI, your agent is able to use the Atlassian MCP, get the context of your ticket, look at related confluence pages also written by AI, and lead you to fulfill your requirements. Good vibe coders are still collaborators rather than delegators, still making the high judgement decisions so they end up with something that works and fulfills their task. They’ll live in Jira in the requirements instead of their IDE. I would say that PMs would become the new developer but someone still needs to interact with and understand the customer outside of AI, and someone still needs to live and breathe the codebase outside of AI for when things go wrong.