Three Claude Code Cloud Tasks Running in Parallel — and a PR Watcher That Fixes Itself

One --cloud command per task spawns an independent cloud VM. Stack three in a row and all three run in parallel while you stay in your editor.

# These three execute simultaneously in separate cloud VMs
claude --cloud "Fix the flaky test in auth.spec.ts"
claude --cloud "Update the OpenAPI docs in docs/api.yaml"
claude --cloud "Refactor the logger to use structured output"

Run /tasks inside any Claude Code session to monitor all three sessions at once, or check them at claude.ai/code from your phone.

Auto-fix: the PR that patches itself

When each session opens a PR, you can turn on auto-fix: teleport into the session (or paste the PR URL into it) and run /autofix-pr. Claude subscribes to GitHub activity on that PR. When a check fails, Claude investigates and pushes a fix; when a reviewer leaves a comment, Claude resolves or responds to it. You don't need to babysit the PR.

From the terminal (while on the PR's branch):

/autofix-pr
# Claude detects the open PR with gh, spawns a web session,
# and turns on auto-fix in one step

Two things to do before you --cloud

1. Push first. --cloud clones the remote at your current branch — local commits that aren't pushed won't be in the cloud session.
2. Check rate limits. Three parallel sessions consume proportionately more of your account's rate limit. For long-running tasks, stagger them by a few minutes if you're near your limit.

When this pattern pays off: large refactors you can decompose by file or subsystem, independent bug fixes on different features, or running the test-and-fix loop in the cloud while you continue writing new features locally.

Sources: Claude Code on the web — code.claude.com · Auto-fix pull requests — code.claude.com