The query is simple. You already run Claude Code. You want the session to keep going when the laptop lid closes.
There are three hosted paths as of 15 September 2026. They all open a GitHub pull request. They do not all run the same extras.
1. Claude Code on the web
Anthropic hosts Claude Code in an isolated VM. Connect GitHub, submit a task, review the PR. Official docs still call this a research preview.
Limits that matter: GitHub is required to push. Zero Data Retention orgs cannot use cloud sessions. User-local ~/.claude does not carry over. Put durable instructions in the repo.
Source: Use Claude Code on the web.
2. Rush Cloud
Rush runs the same Claude Code binary, plus Codex and OpenCode, in a Project your teammates can join. The run is isolated. The trajectory is kept. A coding Task that cannot prove the PR is needs_review.
Start from the console at cloud.getrush.ai or:
rush cloud run claude-code owner/repo --task "fix the flaky test"
Sixty compute minutes are included per user per calendar month. Compute after that is metered.
The longer comparison: Rush Cloud vs Claude Code on the web and Best way to run Claude Code in the cloud.
3. GitHub's third-party Claude agent
GitHub documents an Anthropic Claude agent that can run on GitHub as a public preview. Use it when the trigger must stay a GitHub issue and you accept preview status.
Source: About third-party coding agents.
What to put in the repo
Wherever the VM lives, commit CLAUDE.md, .mcp.json, and any skills. Laptop dotfiles do not travel. That is true on Anthropic's web product and on Rush.
The MCP matrix for every major cloud agent is on Cloud coding agents with MCP.
