We introduce a verification system that prevents errors in AI collaboration through 'Plan Mode,' which requires AI agents to obtain human approval before modifying code.
Imagine you hired a contractor for a home renovation, but the carpenter tore down all your walls without a word and only then asked, “So, how should we fix this?” You would be incredibly flustered and angry. The AI coding tools we use are no different. You might ask an AI to “build this feature,” but if it starts hacking away at your code without rhyme or reason, you could be in for a big headache.
With recent advancements in AI, we have entered the era of ‘agents’—AI that can judge and perform tasks autonomously. But how do we ensure these agents move according to our intentions without making mistakes? Today, we are going to talk about a safety mechanism called ‘Plan Mode,’ which forces AI to write a ‘plan’ before it modifies any code.
Why is this important?
For those using AI in their daily lives, this is a critical issue. If an AI unexpectedly alters the payment function of a website or accidentally deletes an essential system configuration file, your operations could be paralyzed instantly.
Although AI might appear to think and act like a human, it often fails to understand the ‘context’ of our situation 100%. Therefore, a process where a human reviews a plan in advance and approves it, saying, “Yes, proceed with modifications in this direction,” is essential before the AI touches any code. Through this, we can preemptively prevent catastrophic mistakes that an AI might make.
Easy to Understand: ‘Plan Mode’ as a Design Review Process
Think of ‘Plan Mode’ as a ‘design review process’ before construction begins.
- Exploration Phase: The AI agent reads your computer (codebase) to investigate what is needed. During this stage, it only has ‘read-only’ access. It has absolutely no permission to modify or delete files. Source: PlanMode: Make ClaudeCodeThink BeforeItTouches…
- Planning Phase: The AI writes a detailed plan of what it intends to change. It is similar to an architect showing you the blueprints before construction starts.
- Approval Phase: You review this plan and press the ‘approve’ button if it meets your requirements. Only after approval does the AI finally begin modifying the code. Source: Google Antigravity use case - The HQ Digital
By doing this, a human can stop the AI before it tears down the wrong wall. In fact, many secure workflows strictly prohibit AI from coding spontaneously without a plan. Source: arXiv Review Paper Harness
Current Level of Verification
In the current AI development field, verification doesn’t just end with plan approval; it includes an even tighter net of checks.
-
Emergence of Reviewer Agents: There are ‘reviewer agents’ sophisticated enough that a human doesn’t need to check every single line of code after the AI finishes it. These agents automatically verify whether the AI implemented the code according to the plan by comparing the code to the original plan. [Source: Two Gates and a Night Shift Vinny Carpenter](https://vinny.dev/blog/2026-07-06-two-gates-and-a-night-shift/) - Enhanced Security: Companies that prioritize security force AI to test its proposed modifications only within the scope approved by the customer. It is a rule that says, “Don’t just fix it—verify that it is safe within this scope before fixing it.” Source: Oracle Announces AI Security Mesh Powered by OpenAI Cyber Models
What will happen in the future?
In the future, using ‘plans’ as a common language when collaborating with AI will become a daily routine. While it is mainly used in coding today, this ‘Plan Mode’ is expected to become an essential standard for when AI handles professional tasks such as document writing, accounting, and data analysis. When you assign a task to an AI, the first thing it will present will be a plan, saying, “This is how I intend to handle the task.”
MindTickleBytes’ AI Reporter perspective: Technology advances rapidly, but safety is a value that cannot be compromised. This ‘verification system’ that forces AI agents not to exceed human instructions is an essential ‘fence of trust’ required for AI to be fully integrated into our daily lives.
References
- Making Cursor’s agent write plans as artifacts so I can comment on them inline
- arXiv Review Paper Harness
- PlanMode: Make ClaudeCodeThink BeforeItTouches…
- Google Antigravity use case - The HQ Digital
- Oracle Announces AI Security Mesh Powered by OpenAI Cyber Models
-
[Two Gates and a Night Shift Vinny Carpenter](https://vinny.dev/blog/2026-07-06-two-gates-and-a-night-shift/)
- Allows the AI to automatically complete deployment
- Ensures the AI gets human approval before modifying code
- Doubles the AI's processing speed
- Humans write all the code themselves
- Utilizing a separate reviewer agent and CI tools
- Deploying without AI approval
- Applying after testing only within the scope approved by the customer
- AI judging for itself and applying immediately
- Applying first and checking later