2 min lesson
Send CI-482 to a cloud subagent
Send CI-482 to a cloud subagent, inspect its branch and test output, then use /babysit only on the named pull request.
Check your understanding
Complete the practice "Send CI-482 to a cloud subagent, then babysit its pull request".
Outcome: The final diff stays inside the retry package, CI-482 is reproduced and fixed, and the pull request is ready for a human merge decision.
Send CI-482 to a cloud subagent, then babysit its pull request
Clean context, cloud branch, checked pull request
SayI am fixing the billing page locally. CI-482 is an unrelated API retry failure with its own test and file boundary.
Type
/in-cloud In acme/api on release, reproduce CI-482 in packages/api/retry. Use the attached failure output. If the fix stays in that package and its tests, implement it, run npm test -- api-retry.test.ts and open a draft PR. Do not touch billing or shared config.DoSubmit the task from the Agents WindowCursor's surface listing your agent runs; open a run to read its diff and search transcripts from the command palette. Press Enter for the full definition. and keep the local billing task open.
SeeThe cloud subagent starts with clean context in its own VM and branch. The parent task continues locally.
DoOpen the cloud run details and inspect its repository, environment, branch and first test output.
SeeThe run uses the api-ci cloud environment and the brief supplies the CI evidence. It does not depend on the parent conversation or a local MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition. server.
Type
/babysit PR #842. Address review feedback and failing checks only inside packages/api/retry and its tests. Rerun npm test -- api-retry.test.ts. Stop if the requested change crosses that boundary.DoUse /babysit only after PR #842 exists and its remaining work is explicit.
SeeThe cloud agent works through review feedback, conflicts and failing checks on the named pull request, then reports what remains.
DoOpen PR #842. Read its base and head branches, changed files, review thread and test output, then rerun the targeted test before merge.
SeeThe final diff stays inside the retry package, CI-482 is reproduced and fixed, and the pull request is ready for a human merge decision.
Learn more
Optional practice
Test yourself on Send CI-482 to a cloud subagent
QWhat should be true when you finish the cloud subagents practice?