# Planning Warp has native planning functionality that helps you break down complex engineering tasks into structured, executable steps. Planning is tightly integrated with Warp's coding agent and provides a persistent plan editor, version history, selective execution, and deep links into your workspace. {% embed url="" %} *** ### Creating a plan You can generate a plan using the `/plan` [slash command](https://docs.warp.dev/agent-platform/capabilities/slash-commands) or by asking the agent in natural language.

Prompting the agent to create a plan using the slash command.

The agent then creates a structured plan inside Warp’s native rich text editor, which is designed for long, multi-step workflows. The editor includes clean formatting, inline code blocks, and clickable file paths so you can open referenced files immediately in Warp (see below) or in your external editor. ### Reviewing and editing Once a plan is generated, you can review it, reorganize steps, or refine details. You can edit the document manually or ask the agent to revise sections for you.

Any update made by the agent **creates a new version**. Version history lets you compare past iterations and restore an older version if you want to revert your approach, preserving a clear decision trail as the plan evolves.

### Executing a plan When you’re ready to start implementing, prompt the agent to run the plan. You can ask it to execute the full set of steps or only a specific section, such as “Implement phase 1 of the plan.”

Manually referencing the plan using @ to kickoff the plan.

The agent applies changes incrementally and updates files as it proceeds. This makes it easy to validate early steps before moving forward, adjust the plan mid-run, or try alternative paths without committing to the full workflow. If you revise the plan while the agent is running, you can notify it directly; the agent will adjust its execution based on your updates.

Option to pass new plan to agent if plan changes during runtime.

### Monitoring progress While the agent is running, you can reopen the plan at any time by selecting **View plan** in the input. You can also follow each change in real time through the [Code Review](https://docs.warp.dev/code/code-review) panel and add comments or guidance using [Interactive Code Review](https://docs.warp.dev/agent-platform/local-agents/interactive-code-review).

Monitoring progress with the task list and plan view.

This gives you clear oversight, helps confirm expected behavior, and lets you intervene quickly if something needs correction. ### Saving and sharing Warp automatically saves all plans in the *Plans* folder in [Warp Drive](https://docs.warp.dev/knowledge-and-collaboration/warp-drive/). You'll see a confirmation when your plan is synced.

Plans are automatically synced to Warp Drive.

You can export any plan as Markdown, check it into your repository, or share a link—useful for GitHub PRs, design reviews, or async collaboration.

Because plans persist in Warp Drive, you can return to them later, reuse them for new work, or treat them as documentation for ongoing projects. This is also naturally passed to the agent as context.

Plans are accessible directly from the Warp Drive side panel.

You can configure whether your plans will be automatically added and synced to Warp Drive in your [Agent Profiles & Permissions](https://docs.warp.dev/agent-platform/capabilities/agent-profiles-permissions) under **Settings** > **AI** > **Agents** > **Profiles**.

### Using plans across conversations Plans are reusable across tasks and sessions. You can reference them in future prompts, continue where you left off, or build follow-up plans that rely on earlier work. The **@plans** command helps you quickly search for and reopen previously saved plans, making planning a consistent part of your development workflow rather than a one-off step. Learn more about attaching context using @ [here](https://docs.warp.dev/agent-platform/local-agents/agent-context/using-to-add-context).