# Build the plan in a fresh context

**URL:** <https://forum.cursor.com/t/build-the-plan-in-a-fresh-context/158649>\
**Category:** Feature Requests\
**Tags:** context, plan-mode\
**Created:** [April 21, 2026, 5:49pm UTC](https://forum.cursor.com/t/build-the-plan-in-a-fresh-context/158649 "2026-04-21T17:49:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![airanthem](https://avatars.discourse-cdn.com/v4/letter/a/eb8c5e/32.png) [@airanthem](https://forum.cursor.com/u/airanthem)\
**Post date:** [April 21, 2026, 5:49pm UTC](https://forum.cursor.com/t/build-the-plan-in-a-fresh-context/158649/1 "2026-04-21T17:49:10Z")

</div>

### Feature request for product/service

Cursor IDE

### Describe the request

OpenAI Codex released a new feature in the latest version [v0.122.0](https://github.com/openai/codex/releases/tag/rust-v0.122.0)

> Plan Mode can start implementation in a fresh context, with context-usage shown before deciding whether to carry the planning thread forward

I consistently use the Opus model to create a highly comprehensive plan, and then switch to Auto mode for the build phase. This approach gives me the best balance across quality, time, and cost.

The only downside is that, to avoid context contamination, I have to manually save the plan and start a new session each time, which is quite cumbersome. It would be ideal if the planning mode could natively support something like Codex—executing the build in a fresh context.

---

<div class="post-metadata">

**Author:** ![Ben\_Rugg](https://avatars.discourse-cdn.com/v4/letter/b/8491ac/32.png) [@Ben\_Rugg](https://forum.cursor.com/u/Ben_Rugg)\
**Post date:** [May 14, 2026, 7:16pm UTC](https://forum.cursor.com/t/build-the-plan-in-a-fresh-context/158649/3 "2026-05-14T19:16:52Z")

</div>

I came here to submit this feature request! Yes, this would be a very helpful update. And I’ll just note that this has been requested before!:

> [@Plan mode should 'Build' in a subagent or new chat](https://forum.cursor.com/t/plan-mode-should-build-in-a-subagent-or-new-chat/152993):
>
> Feature request for product/service Cursor IDE Describe the request When you click build on a plan, it builds in the chat that you are currently in by default. This is not good if you have been using your current chat to refine the plan, where there could be a lot of unnecessary context for building the plan. Instead, when you click ‘build’ on a plan, ideally it should build within your current chat, but in a subagent rather than in the main chat, so that you can continue to have a conversation…

and

> [@Implement a plan in a new thread](https://forum.cursor.com/t/implement-a-plan-in-a-new-thread/156918):
>
> Feature request for product/service Cursor IDE Describe the request I’d like to propose a workflow improvement around plan mode and context management in Cursor. Right now, when I create a detailed plan within a thread, it often consumes a large portion of the available context. That’s fine for planning, but when it comes to implementing the plan, the model already has a lot in its context, and the implementation may end up happening in the model’s “dumb zone.” I’d love to see the ability to …

and more, but it won’t let me post more than 2 links 😅