Local vs Cloud Runs, Streaming and Resume

Done means you can choose local or cloud runtime and handle run lifecycle cleanly.

The same agent loop can run in a terminal, script, CI job or SDK-backed internal tool.

Use SDK runs when a programmatic agent needs durable execution or interactive streaming. 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.

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.

1. 1Choose local for tight local context or cloud for background execution.
2. 2Stream output when humans need progress visibility.
3. 3Use wait, cancel, resume and request IDs deliberately.
4. 4Attach branch, PR or artifact behavior for cloud runs.

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.

Verification decides the next move.

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.