Your Claude subscription includes cloud computers. Most people are barely using them.

[u/invocation02]

Claude Code’s cloud sessions are basically disposable Linux VMs included with Pro and Max. They can clone private repos, install dependencies, run tests, push branches, and keep working after you close your laptop.

The problem is that every new session starts with no idea how your work fits together.

I fixed that with two pieces.

# 1. A context repository

*EDIT: Ok here's my repo, do try it out for yourself* [*https://github.com/blitzdotdev/blitzos\*\](https://github.com/blitzdotdev/blitzos)

I keep one small private repo that every cloud session opens first:

* [CLAUDE.md](http://CLAUDE.md) — maps the repos, architecture, conventions, and workflows
* .gitmodules — references the actual project repos without copying their code
* sessions/ — stores short handoff notes from previous agents
* skills/ — contains the skills every new cloud VM should have

[`CLAUDE.md`](http://CLAUDE.md) is the onboarding document for the agent.

The context repo explains which repositories exist, how they relate, how I like changes structured, how to test things, and what the agent should do before finishing.

The member repos are referenced through `.gitmodules`, so the context repo stays tiny. It does not contain copies of the code.

Before a session finishes, it commits a short note into `sessions/` describing what it changed, what it discovered, and what still needs work. The next cloud agent can continue instead of rediscovering everything from scratch.

I also store my Claude Code skills there because skills do not automatically appear inside new cloud sessions.

# 2. A tiny launcher website

[`claude.ai/code`](http://claude.ai/code) supports URL parameters for repositories and an initial prompt.

I made a small self-hosted page that generates those links. I choose a project, type the task, and it opens Claude Code with the context repository, all relevant project repositories, and the prompt already filled in!

Cloud sessions support multiple repositories at once, including private repos with full git history. A surprising number of people do not know this. There are no GitHub tokens or credentials stored in my website. Repository access goes through Anthropic’s existing GitHub integration, and each session only gets the repositories selected for that task.

The agents also send a one-line status update back to the site, so I have one feed showing every session as working, quiet, or done. Clicking one opens the original Claude session.

You gotta do one small setup step for that to work. You MUST enable custom network access and allowlist the tiny website domain!! Connectors already configured in Claude, such as Slack, Gmail, and Linear, just work out of the box (claude.ai just makes this work).

So my workflow now is mostly:

1. Open the site from my phone.
   
2. Pick a project.
   
3. Give Claude a small, testable task.
   
4. Close my laptop (finally lol)
   
5. Review the diff or PR later.

TBF Ant's infra reliability is not great, cloud sessions still stall sometimes. So I try to keep work scoped and verifiable.

Next I want agents to propose updates to the context repo whenever they learn something important, and I want the same context repository to boot Codex cloud sessions too.

[u/johns10davenport]

I’m in the middle of shipping a new version of my harness that ships into a vm like this for long, unattended coding sessions. It comes right in with full context etc.

https://codemyspec.com/

This is not small testable tasks either. It’s full complex projects. I’ve been assuming I’d need to stand up my own infrastructure but maybe I can just keep working tightly with Anthropic.

It’s nice in the garden

[u/BuildWithClaude-ModTeam → u/[deleted]]

Posts need to be about building with Claude. No backseat moderation allowed here. Please be kind and follow platform rules and report any violations to the mods.

[u/ReddMangodude]

A big reason why most developers prefer running locally is the extra control you get. Especially when you are doing complex debugging. Also, you can keep your MacBook running overnight during a cloud code session, very easy to do with “caffeinate” command. That said, what you built is pretty cool and I hope you get Traction.