Docs say to restart a Cloud Agent, but where is the restart option?

Support Help
,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

The Cloud Agents docs, under “My secrets aren’t available to the cloud agent,” say:

Try restarting the cloud agent after adding new secrets

I added a new runtime secret to my cloud environment, but the existing agent still can’t see it. I can’t find anywhere to restart the existing Cloud Agent or its environment in the web UI or Cursor desktop.

Where is the restart option? Can it be done from the CLI inside the cloud desktop? If “restart” means creating a new agent or rebuilding the environment, could the docs say that and include the exact steps?

Steps to Reproduce

  1. Start a Cloud Agent.
  2. Add a new runtime secret in the cloud environment settings.
  3. Check the existing agent terminal; the new secret is unavailable.
  4. Follow the docs’ advice to restart, but no restart option can be found.

Expected Behavior

A way to restart the existing Cloud Agent/environment so it picks up newly added secrets, or clear documentation explaining exactly what “restart” means and how to do it.

Operating System

MacOS

Version Information

Cursor desktop 3.19.7 on macOS. Cloud Agents web UI in Arc at cursor.com/agents.

For AI issues: which model did you use?

N/A — this concerns the cloud environment and documentation.

Additional Information

I checked the web agent menu and Cursor desktop. The cloud terminal also does not have the agent, cursor-agent, or cursor CLI commands available. I would like to keep working in the existing agent with the newly added secret.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey @ColemanDunn, thanks for the report, and you’re right that the docs wording is confusing here.

Secrets are attached to a cloud agent at the moment it starts, so an agent that was already running when you added the secret won’t see it. There isn’t a restart button for an existing agent right now (and the CLI isn’t installed inside the VM on purpose), so “restart” in the docs really means “start a new agent”. We’ll get that line fixed.