Feedback buttons (Approve/Deny/Send) don't work when running via SSH + Cursor

[mdthewzrd]

Bug

When running Pi via SSH through Cursor IDE terminal, the Plannotator plan review browser opens via Cursor's port forwarding (BROWSER env is set to Cursor's helper script). The page loads and renders correctly, but clicking Approve, Deny, or Send Feedback buttons does nothing — the button click doesn't register or the POST doesn't route back to the server.

Environment

• Pi running on remote Linux server (accessed via Tailscale SSH)
• Cursor IDE terminal (SSH)
• BROWSER=/home/mdwzrd/.cursor-server/bin/linux-x64/.../browser.sh
• Plannotator 0.19.1
• The server opens a local HTTP server on a random port (e.g. localhost:37639)
• Cursor intercepts the browser open and port-forwards to local desktop
• Page loads fine, but button clicks have no effect
• Have to manually paste annotations to the agent as workaround

Expected

Buttons should submit feedback back to the Plannotator server.

Actual

Buttons are unresponsive — no network request reaches the server. The waitForDecision() promise never resolves. Tool returns 'No result provided'.

Workaround

Paste annotations directly to the Pi agent instead of using the UI.

[mdthewzrd]

Update: Found the actual issue

The Plannotator server starts on a random local port and opens a browser via Cursor's port forwarding. The server is held in-memory within the Pi process.

The problem: if the Pi session restarts (or the waitForDecision() promise never resolves), the Plannotator server dies. The browser tab stays open pointing at a dead server, so buttons stop working. There's no error — just silent failure.

Additionally, the tool returns No result provided instead of a timeout or error, making it hard to diagnose.

Suggestions:

1. Add a timeout to waitForDecision() — if no response in N minutes, return a timeout error instead of hanging forever
2. Add a heartbeat/health-check endpoint to the plan review server so the browser can detect when the server is gone
3. Show a "Server disconnected" banner in the browser UI when the heartbeat fails
4. Return a proper error from the tool instead of No result provided when the server dies

[backnotprop]

Hey, thank you for reporting. I haven't actually tried any of this in Cursor, but there's been a lot of interest.

I do have a subscription, so I'll give this a shot.