The distinction between "AI as chatbox attached to an editor" and "AI as agent that collaborates across the whole development workflow" is where most of the interesting tooling exploration is happening right now. The chatbox model is familiar and low-risk; the agentic model is more powerful but requires different assumptions about trust, verification, and the division of responsibility.

The Plan Mode / Debug Mode / Review Mode differentiation is thoughtful — it acknowledges that different tasks require different levels of agent autonomy and different kinds of human oversight. Giving the developer explicit control over which mode is active is a meaningful design choice.

The Agile Vibe Coding Manifesto's principle that "humans remain accountable for software systems" is directly relevant here: accountability doesn't mean doing everything yourself, but it does mean maintaining enough understanding and control to be genuinely responsible for the outcomes. Different agent modes with different oversight requirements is one way to structure that.

The "rules to inject repository conventions" feature is particularly interesting for teams: https://agilevibecoding.org