Plan mode "Build" button doesn't update to "Built" after implementation

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I used Plan mode to create a multi-phase implementation plan (Soundtrack Catalog Matching). I then switched to Agent mode and built out all the phases across multiple conversation sessions – the code is written, committed, pushed, and actively running in production on 3 VMs.

When I go back to the Plan, the “Build” button still shows as unbuilt (no checkmark, same shading as a fresh plan). I expected it to show “Built” with the green checkmark since the work is complete.

It seems like the Plan mode doesn’t track completion status when the implementation happens in Agent mode or across multiple sessions. The button state appears to be purely session-based rather than reflecting the actual state of the codebase.

Steps to reproduce:

Create a plan in Plan mode
Switch to Agent mode and implement the plan
Return to the Plan – “Build” button still shows as unbuilt
Expected: Build status reflects that the planned work has been implemented

Actual: Button remains in the unbuilt state indefinitely

Version: Opus 4.6 (as shown in the Plan header)

Steps to Reproduce

Create a plan in Plan mode
Switch to Agent mode and implement the plan
Return to the Plan – “Build” button still shows as unbuilt
Expected: Build status reflects that the planned work has been implemented

Actual: Button remains in the unbuilt state indefinitely

Expected Behavior

Expected: Build status reflects that the planned work has been implemented

Operating System

Windows 10/11

Version Information

Version: 3.0.13 (user setup)
VSCode Version: 1.105.1
Commit: 48a15759f53cd5fc9b5c20936ad7d79847d914b0
Date: 2026-04-07T03:05:17.114Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Opus 4.6

Does this stop you from using Cursor

Yes - CursoCursor is usable

6

Hi @drryansantangelo

This is actually expected behavior with how Plan mode currently works. The “Build” button and its “Built” status are tied to a specific workflow: when you click Build on a plan, Cursor registers that composer session as the builder and tracks completion through that link. If you switch to Agent mode and implement the work separately, that link is never established, so the plan UI has no way to know the work was completed.

The intended workflow is: create a plan in Plan mode, then click Build on the plan to execute it. That way the status tracks correctly.