Plan mode always falls back to refining the latest existing plan, with no visible way to start a fresh plan in the same thread.
Description When a thread already contains an older proposed plan, switching the thread back into Plan mode automatically enters the “refine latest plan” flow. The composer/banner treats the latest settled proposed plan as the active target by default, so sending in plan mode reuses that old plan instead of letting the user start a new planning turn.
This makes plan mode sticky to the most recent prior plan in the thread. Users who want to create a brand-new plan in the same thread cannot do that explicitly and are pushed into refining the previous one.
Expected If a thread already has a prior plan, plan mode should still offer an explicit choice:
refine/use latest plan
start a new plan
The chosen mode should be visible in the composer UI and should affect what gets dispatched.
Actual Entering plan mode on a thread with an older plan immediately behaves like “refine latest plan,” with no visible control to switch to “new plan.”
Repro
Open a thread and generate a proposed plan.
Leave that thread and later return to it.
Switch the thread into Plan mode again.
Try to create a completely new plan.
Observed result The composer/banner assumes the existing latest plan is the active target and treats the next send as a follow-up/refinement of that plan.
Impact This makes long-running threads awkward to use for multiple planning cycles and can cause users to accidentally refine an outdated plan when they intended to start over.
Plan mode always falls back to refining the latest existing plan, with no visible way to start a fresh plan in the same thread.
Description When a thread already contains an older proposed plan, switching the thread back into Plan mode automatically enters the “refine latest plan” flow. The composer/banner treats the latest settled proposed plan as the active target by default, so sending in plan mode reuses that old plan instead of letting the user start a new planning turn.
This makes plan mode sticky to the most recent prior plan in the thread. Users who want to create a brand-new plan in the same thread cannot do that explicitly and are pushed into refining the previous one.
Expected If a thread already has a prior plan, plan mode should still offer an explicit choice:
refine/use latest plan
start a new plan
The chosen mode should be visible in the composer UI and should affect what gets dispatched.
Actual Entering plan mode on a thread with an older plan immediately behaves like “refine latest plan,” with no visible control to switch to “new plan.”
Repro
Open a thread and generate a proposed plan.
Leave that thread and later return to it.
Switch the thread into Plan mode again.
Try to create a completely new plan.
Observed result The composer/banner assumes the existing latest plan is the active target and treats the next send as a follow-up/refinement of that plan.
Impact This makes long-running threads awkward to use for multiple planning cycles and can cause users to accidentally refine an outdated plan when they intended to start over.