Cloud Agent vs grok CLI
Choose the worker for coding or heavy multi-step work: Cursor Cloud
Agent, the local grok CLI, or both.
Iron law
Builds go to the grok CLI, Cursor Cloud Agents, or both. Do not
implement with a bot token; hand the build to one of those workers.
Hand-off
- Hand off the whole ticket.
- Let the worker own the implementation loop.
- verifier checks the final result.
How remote agents and local CLIs fit the process:
Workers. A worker's pull request
into this repo still goes through intake:
Workers.
Default split
| Work |
Use |
| Design, review, scratch work, or build-quota research on this machine |
grok CLI |
| A change that must land as a remote branch or pull request |
Cursor Cloud Agent |
| Greenfield work with no repository named |
Cloud Agent new_repo |
| SDLC artifacts that live in the operator's private SDLC repository |
That repository, often through a Cloud Agent pull request |
| Files that exist only on a host with no remote checkout |
grok CLI or shell on that host |
| Windows, or any host outside the workspace |
Off limits unless the operator approved that host: Never |
Keep product GitHub repositories separate from the operator's private SDLC
repository.
Prefer Cloud Agent when
Use Cursor Cloud Agent when any of these holds:
- The deliverable is a branch or a pull request on a connected remote
repository.
- The deliverable lands in the operator's private SDLC repository,
connected as a remote repository.
- The work needs Cursor source control or a cloud VM.
Credit degrade
If a requested Cloud Agent run fails on usage, credits, quota, or
billing, that request also approves the grok CLI for the same goal.
Fall back without a new ask.
If Cloud Agent fails because of usage, credits, quota, or billing:
- Say once that Cloud Agent failed on usage, credits, quota, or billing.
- Fall back to the grok CLI for the same goal.
- If a remote pull request was required, produce the patch on this
machine.
- If step 3 applies, open or hand off the pull request from an approved
host that already has credentials, or give the operator a branch-ready
diff.
- If the grok CLI is also unavailable, stop and report both blockers.
- Do not retry in a tight loop. Fall back as above.
- Do not implement with a bot token, including for a large patch. Use
the grok CLI or a branch-ready diff.
- Do not work around the block with cookies or a Windows host. Stop and
report the blocker.
Launch
- If the repository is ambiguous, confirm it with the operator.
- Launch with a clear goal, the constraints, and what done looks like.
- On launch and on reply, prefer Grok 4.7 unless the operator names
another model.
- Do not poll. Wait for the run to complete, then resume.
- Follow up with a reply.
- Interrupt a run only when asked.
- Keep bank, mail, password-store, VPN, and chat secrets out of the
prompt.
For the grok CLI, the run steps are in grok-acp.
Load it when the operator opts in to Grok Build over ACP, or when Credit
degrade falls back to the grok CLI.
Roles
Role names and jobs: Roles. Tracker writes:
Tracker. Host lock:
Never.
1---2name: cursor-cloud-agents-when3description: use this when choosing Cursor Cloud Agent or the local grok CLI for coding or heavy multi-step work — Cloud Agent for a remote repo or pull request, the grok CLI for work on this machine under build quota, and the operator's private SDLC repository for artifacts that live there. if Cursor credits are empty, degrade to the grok CLI. do not use on your own initiative, and do not implement with a bot token.4metadata:5 source: https://skillmd.com/skills/alexderz/cursor-cloud-agents-when6---78# Cloud Agent vs grok CLI910Choose the worker for coding or heavy multi-step work: Cursor Cloud11Agent, the local grok CLI, or both.1213## Iron law1415**Builds go to the grok CLI, Cursor Cloud Agents, or both. Do not16implement with a bot token; hand the build to one of those workers.**1718## Hand-off19201. Hand off the whole ticket.212. Let the worker own the implementation loop.223. **verifier** checks the final result.2324How remote agents and local CLIs fit the process:25[Workers](../sdlc/references/subagents.md#workers). A worker's pull request26into this repo still goes through intake:27[Workers](../sdlc/references/intake.md#workers).2829## Default split3031| Work | Use |32| --- | --- |33| Design, review, scratch work, or build-quota research on this machine | grok CLI |34| A change that must land as a remote branch or pull request | Cursor Cloud Agent |35| Greenfield work with no repository named | Cloud Agent `new_repo` |36| SDLC artifacts that live in the operator's private SDLC repository | That repository, often through a Cloud Agent pull request |37| Files that exist only on a host with no remote checkout | grok CLI or shell on that host |38| Windows, or any host outside the workspace | Off limits unless the operator approved that host: [Never](../security-hardening/SKILL.md#never) |3940Keep product GitHub repositories separate from the operator's private SDLC41repository.4243## Prefer Cloud Agent when4445Use Cursor Cloud Agent when any of these holds:4647- The deliverable is a branch or a pull request on a connected remote48 repository.49- The deliverable lands in the operator's private SDLC repository,50 connected as a remote repository.51- The work needs Cursor source control or a cloud VM.5253## Credit degrade5455If a requested Cloud Agent run fails on usage, credits, quota, or56billing, that request also approves the grok CLI for the same goal.57Fall back without a new ask.5859If Cloud Agent fails because of usage, credits, quota, or billing:60611. Say once that Cloud Agent failed on usage, credits, quota, or billing.622. Fall back to the grok CLI for the same goal.633. If a remote pull request was required, produce the patch on this64 machine.654. If step 3 applies, open or hand off the pull request from an approved66 host that already has credentials, or give the operator a branch-ready67 diff.685. If the grok CLI is also unavailable, stop and report both blockers.6970- Do not retry in a tight loop. Fall back as above.71- Do not implement with a bot token, including for a large patch. Use72 the grok CLI or a branch-ready diff.73- Do not work around the block with cookies or a Windows host. Stop and74 report the blocker.7576## Launch77781. If the repository is ambiguous, confirm it with the operator.792. Launch with a clear goal, the constraints, and what done looks like.803. On launch and on reply, prefer Grok 4.7 unless the operator names81 another model.824. Do not poll. Wait for the run to complete, then resume.835. Follow up with a reply.846. Interrupt a run only when asked.857. Keep bank, mail, password-store, VPN, and chat secrets out of the86 prompt.8788For the grok CLI, the run steps are in [`grok-acp`](../grok-acp/SKILL.md).89Load it when the operator opts in to Grok Build over ACP, or when Credit90degrade falls back to the grok CLI.9192## Roles9394Role names and jobs: [Roles](../sdlc/SKILL.md#roles). Tracker writes:95[Tracker](../sdlc/SKILL.md#tracker). Host lock:96[Never](../security-hardening/SKILL.md#never).