Cloud Agents: “Environment ready to save” keeps reappearing every ~30s after environment is already saved — no way to clear stale proposal

[George_Mortley]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After successfully saving a personal Cloud environment, the “Environment ready to save” popup keeps reappearing approximately every 30 seconds in the same Project conversation.
The environment itself is already saved and working:

• Cloud agents boot from the active succeeded build
• Environment secret VPS_SSH_PRIVATE_KEY works
• Agents can SSH to my VPS and run work
  So this is not “environment not saved.” It looks like a stale conversation-attached proposal left over from an earlier propose-environment-json call during setup. Saving did not clear that proposal state, and the Desktop UI keeps polling/resurfacing the card.
  There is also no agent MCP tool to list, cancel, reject, or dismiss a proposal — only propose-environment-json, which creates/updates proposals and would make the card worse if called again.

Steps to Reproduce

1. In a Project / Cloud Agent conversation, run environment setup that calls propose-environment-json (and optionally trigger-environment-build).
2. Wait for a SUCCEEDED build and Save the environment in the Portal/Desktop Save card (personal scope).
3. Confirm the environment is usable: activeBuild present, new/existing Cloud agents work, secrets attached.
4. Stay in the same Project conversation.
5. Observe “Environment ready to save” reappearing roughly every ~30 seconds even though nothing needs saving.

Expected Behavior

Expected Behavior

• After a successful Save (or when activeBuild already matches the proposed build), the outstanding proposal is cleared.
• The Save card does not keep reappearing.
• Ideally: an agent/API or UI action exists to cancel/discard a stale proposal without deleting the saved environment.

Actual Behavior

• Saved environment remains healthy and usable.
• “Environment ready to save” continues to interrupt every ~30s.
• No supported way for the agent (or me) to clear only the stale proposal.
• Dismissing/saving again is not a durable fix; the card returns.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.25.6
Commit: f0df777c412b670d09e3eaf214967d779e67c080
VS Code: 1.128.0
Quality: stable

Additional Information

Identifiers

• Conversation / Project bcId: bc-a2d8f636-af5b-4386-927d-becfd80bbfe7
• URL: https://cursor.com/agents/bc-a2d8f636-af5b-4386-927d-becfd80bbfe7
• Environment public id: f31087e5-cca4-11f1-bec7-b2318963e0b6
• Environment version public id: 189d43c6-ccaa-11f1-bec7-b2318963e0b6
• Environment name: bot-f-vps / george-mortley/bot-f (personal)
• Repo: origin.cursor.com/git/george-mortley/Bot-F
• Active/succeeded build: bld-20261020-7dcd7546-edf3-4cec-be29-b81200b857a7
• Proposal id: unknown (not exposed by agent tools)
• Account: George Mortley / user id 358539435

Requested fix

1. Clear/invalidate the outstanding proposal attached to conversation bc-a2d8f636-… without deleting environment f31087e5-… or secret VPS_SSH_PRIVATE_KEY.
2. Auto-clear proposals when Save succeeds / active build already matches.
3. Add cancel/list proposal APIs (or a Discard action in the UI).

Important constraints

Please do not delete the environment or rotate/remove VPS_SSH_PRIVATE_KEY as remediation.

Does this stop you from using Cursor

Yes - Cursor is unusable

[Colin]

Hey @George_Mortley,

Your environment is saved correctly. All three of your saves on Oct 20 went through with the same build, and nothing is left pending on our side, so there is no proposal that needs clearing.

The card comes back because of how the app decides whether a setup conversation has been saved. When you save from a build, the app only remembers that for as long as the current window stays open. After a restart it can no longer link the saved environment back to this conversation, so it offers Save again whenever the agent goes idle. In a busy Project conversation that is every few minutes, which is why it feels constant. I’ve flagged this to the team.

In the meantime:

1. Clicking Save once after Cursor starts hides the card until the next restart. It re-saves the same build, so your environment, its secret and the active build are untouched.
2. New cloud agents started from your saved environment shouldn’t show the card at all.

There isn’t a way to dismiss the card from the agent side today, so please don’t ask the agent to call the proposal tool again.

[George_Mortley]

Thanks for investigating.

Unfortunately, the suggested workaround does not work.

I have already clicked Save multiple times after starting Cursor, but the environment-saving card continues to reappear every few minutes without restarting the application.

This happens repeatedly within the same Cursor session, so the explanation about the association being lost after restarting doesn’t fully explain what I’m experiencing.

Can you please investigate why the card continues appearing even after I’ve saved the environment during the current session?

Is there any alternative way to permanently dismiss or suppress this card while I continue working in my existing Project conversation?

I don’t want to start a new conversation because it contains substantial development history.

[Colin]

Hey @George_Mortley,

You’re right, and I’m sorry about the earlier workaround. On the version you’re running, clicking Save doesn’t hide this card even for the rest of the session, so it was never going to help. The restart explanation applied to newer code that hasn’t reached a release yet.

Unfortunately there isn’t a way to dismiss this card in an existing conversation today. It doesn’t affect your environment or your agents, so you can keep working in this conversation and ignore it. There’s no need to start a new one or to save again.