Skip to main content
Plan mode was previously called Chat mode. The name was changed to better reflect how the mode is intended to be used before implementation.

​
Overview

Plan mode is Lovable’s planning and reasoning mode. It is designed for moments when thinking is more valuable than immediate execution. You can use Plan mode to ask questions, debug issues, explore ideas, compare approaches, or reason about changes before any code is written. When there is a clear implementation to propose, Lovable creates a formal plan that you can inspect, edit, and refine. Plan mode never modifies your code. Mental model:
  • Plan mode → think, explore, and decide
  • Agent mode → implement
You can enter Plan mode at any time and return to it as often as needed throughout a project. Every message in Plan mode deducts 1 credit.

​
What Plan mode is for

Plan mode is a general-purpose reasoning space for moments when thinking, exploration, or clarity is more valuable than immediate execution. It can reason across multiple steps and inspect files, logs, or other relevant project context as needed. You can use Plan mode to:
  • Explore product or feature ideas before committing to a direction
  • Ask questions about your codebase or existing behavior
  • Investigate bugs, errors, or confusing behavior safely before making code changes
  • Compare multiple approaches and understand tradeoffs
  • Design architecture or database schemas
  • Understand the impact of potential changes before making them
Many Plan mode conversations are exploratory and end with clarity or direction. When a conversation does lead to a concrete change, Plan mode provides a safe way to review and refine the proposed approach before anything is implemented.

​
How to use Plan mode

You can use Plan mode in two ways:
  • Start in Plan mode when beginning a new project or exploring an idea
  • Switch to Plan mode at any point during development to pause execution and think

​
Activate Plan mode

Click Plan next to the message input, then describe what you want to explore or decide. Be specific about what you want to accomplish: 
Add email/password authentication with password reset. 
Users should stay logged in for 30 days. Use Lovable Cloud.
Use it for exploration: 
What's the best way to implement real-time notifications in this project? 
Walk me through the options and their tradeoffs.
Use it for debugging: 
Users report the login form doesn't work on mobile. 
Help me figure out why.
Request detailed breakdowns: 
Break down the implementation of a shopping cart feature. 
What components, database tables, and API endpoints will I need?
Ask for reviews and improvements: 
Review my current authentication setup. 
What security improvements should I make?

​
When Plan mode creates a plan

Plan mode does not always produce a structured implementation plan. A plan is created only when there is a clear implementation to propose. If a plan is generated, it appears in a dedicated Plan view as a readable, structured document. You can open it in full screen to review the entire approach before anything is implemented. A plan typically includes:
  • A high-level overview of the approach
  • Key decisions, assumptions, and constraints
  • Components, data models, and APIs
  • Step-by-step implementation sequencing
  • Optional diagrams such as schemas, flows, or architecture
From the Plan view, you can:
  • Edit the plan directly as markdown to add constraints, remove steps, or rewrite sections
  • Approve the plan when you are satisfied with the approach
You can ask follow-up questions or request changes directly in the chat, and Lovable will update the plan accordingly. When you approve a plan:
  • Lovable switches to Agent mode
  • Implementation begins based strictly on the approved plan
You can return to Plan mode at any time to generate a new plan based on the current state of your codebase.

​
Plans and persistence

When you approve a plan, the latest approved version is saved to .lovable/plan.md. This file represents the current plan that Agent mode will implement, and you can inspect it like any other project file. Earlier plans are not lost. Previous plans remain available in your conversation history and can be reopened in the Plan view for reference or comparison, even though only the most recent approved plan is saved to plan.md. This allows you to:
  • Iterate on ideas over time
  • Compare different approaches
  • Re-plan safely as requirements evolve
  • Help new collaborators understand the reasoning behind implementations

​
FAQ

No. Code changes only happen after you approve a plan and Lovable switches to Agent mode.
The latest approved plan is saved to .lovable/plan.md. Earlier plans remain accessible from chat history.
Yes. Plans are fully editable before approval.
Yes. Earlier plans remain accessible from chat history.
Yes. Plan mode is well suited for investigating issues and deciding on fixes before implementation.
Yes. Every message in Plan mode deducts 1 credit.