With a plan that shows a Build now button, and with CMD+Enter to send enabled, pressing Enter alone in the follow-up message box starts a local plan build instead of inserting a newline / waiting for CMD+Enter to send.
This was previously fixed, but it still happens (regression).
Steps to Reproduce
Open a chat that has an active plan with a Build Locally button showing in the dialog box above the chat.
Ensure send-on-CMD+Enter is enabled (so Enter alone should not send).
Focus the follow-up input under the plan.
Press Enter (not CMD+Enter).
The plan starts building
Expected Behavior
Enter should not trigger Build now. It should insert a newline (or otherwise leave the plan unbuilt) until the user explicitly clicks Build now or uses the intended send shortcut.
Hey @lantrix
I tried the same setup on a current Agents Window build with Submit with ⌘ + Enter on, and plain Enter in the follow-up box only inserts a newline. Build only fires on the chord shown on the button (usually ⌥⌘⏎ when that setting is on). The earlier thread you linked was a different conflict (the old “Try Plan Mode” nudge stealing Cmd+Enter), so this looks like a separate case.
Could you check a couple of things?
Open Cursor Settings → Keyboard, search for Build / plan, and see whether Build Plan (or similar) is bound to plain Enter. A custom binding would survive updates and match what you’re seeing.
When it happens, is the caret clearly in the follow-up input, or could focus be on the Build button itself? (A focused button activates on Enter regardless of the send setting.)
If it still happens with default bindings and focus in the input, a short screen recording would help a lot.