Secrets, Computer Use and Artifacts
Cloud agents need deliberate access, output and evidence policies.
Use the right surface
After this you can pick Cloud capabilities for the right job and define done.
Done means you can grant only the access needed and collect useful evidence.
Cloud agents help when work needs isolation, artifacts, handoff or parallel execution.
Use Cloud capabilities when the task needs credentials, browser/computer use or artifacts for review. Keep the boundary narrow.
Start small. Name the job, attach the context that proves the point and decide what evidence would make the output trustworthy.
Read the loop before touching the controls. The first beat frames the work, the second uses Cursor, the third checks the result and the fourth leaves a handoff someone else can inspect.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Run this loop in a real repo.
- Entry point
- Cloud secrets, computer use, artifacts and remote desktop
- Source
- Cloud capabilities, computer use and privacy governance docs
Use the source as the product reference.
Ask Cursor for an output you can inspect.
If the output cannot be checked, narrow the task before you continue.
A good run leaves a file, setting, screenshot, command result or written claim you can verify.
Takeaway. Done means you can grant only the access needed and collect useful evidence.
Self-check
QWhen should you reach for Cloud capabilities?
Run it
After this you can do the task with clear scope and one proof point.
Treat this as a short practice loop, not a product tour. The task should be small enough that you can inspect the result without trusting the summary.
- 1Identify which secrets or interactive capabilities are necessary.
- 2Grant access through the supported cloud-agent mechanism, including computer use so the agent drives its own mouse on a virtual desktop.
- 3Let the agent run its self-verify loop: make a change, spin up a browser, test it, record a video plus screenshots, and upload them to the PR.
- 4Remove or rotate anything that should not persist.
The exercise is complete only when the proof matches the requested outcome. If the proof is weak, reduce the scope or fix the context instead of adding more instructions.
Keep the task small enough to review.
Artifacts on the PR (video, screenshots, logs) prove the relevant behavior end to end.
Takeaway. Stop when you have proof: Secrets are not written into code or logs..
Self-check
QWhich habit makes this workflow safe to use on a real project?
Check it
After this you can find the first failed check before changing tools.
Verification decides the next move.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Pick a row to see what to look for.
Use the first failure signal as the next prompt. Broad retries usually make the run noisier; a narrow retry gives Cursor a concrete repair target.
No proof means more checking.
Use a real repo or admin setting. Save the prompt, context and proof.
Takeaway. If it fails, find the first failed check.
Self-check
QThe workflow failed. What is the best first move?