{
  "video_id": "reddit_1uvosli",
  "channel_slug": "ClaudeAI",
  "channel_handle": "r/ClaudeAI",
  "title": "I was using Claude Cowork's cloud VMs (free, included in plan) completely wrong. It replaced most of my local workflow once I set them up properly.",
  "url": "https://www.reddit.com/r/ClaudeAI/comments/1uvosli/i_was_using_claude_coworks_cloud_vms_free/",
  "external_url": null,
  "upload_date": "20260713",
  "published_at": "2026-07-13T21:25:44+00:00",
  "transcript": "I think most people are using Claude Code’s cloud sessions as a novelty. You send it a task, watch it do something, then close the tab. That’s how I used them too, until I realized what Anthropic is actually giving us here.\n\nCloud sessions run on real cloud VMs using your existing Claude subscription, with no separate API bill. Each session can clone multiple repos, including private repos, with the full git history. It can install dependencies, run tests, access the internet, and actually execute the code it writes. You can start several at once and manage all of them from the web or your phone.\n\nBasically, Claude gives you a new computer for every task, and you can turn one on from anywhere.\n\nThe big unlock for me was making these computers start with all the context they need instead of explaining my setup again every time.\n\nI created one private “context” repo that pulls together the repos I work across, explains how they relate, and includes my project conventions. I can also give each session only the connections and credentials needed for its specific task.\n\nSo if I ask Claude to fix a flaky checkout test, it can start with the correct repo, staging environment, and ticket. If I ask why signups dropped, it can access the relevant analytics and code, but nothing else.\n\nThe session starts roughly as capable as my laptop, but only gets access to what it needs for that job. Then it keeps working even if my laptop is closed.\n\nThis has completely changed how I use Claude Code/Cowork. I’ve reviewed and merged real PRs from my phone on the train. I’ve started three investigations before lunch, let them run in parallel, and checked the results later that night.\n\nIt feels less like using an AI coding tool and more like running a small engineering team where every agent gets its own computer.\n\nThe annoying part is that making sessions “job-ready” still takes a lot of manual setup. You have to organize the context, connect the repos, scope the credentials, and decide what each session should see. It took me most of a weekend to get everything working properly.\n\nThe raw capability is already there behind a settings toggle. The missing part is making every new VM boot up already understanding your company and your work.\n\nI ended up scripting my setup into basically one command because rebuilding it manually would be miserable. If people are interested, I’ll clean it up and share it.\n\nIs anyone else using cloud sessions this way? What work have you moved off your laptop, and what’s still stopping you?\n\n*EDIT: Published my setup here as a skill, check it out:* [*https://github.com/blitzdotdev/blitzos*](https://github.com/blitzdotdev/blitzos)\n\n\n\n--- Top Comments ---\n\n\n[14 upvotes] Please eli5.  This sounds very interesting but I’m too dumb to follow this well.\n\n[4 upvotes] Can I connect to you internal network? Company network? If so will it be the security hole? \n\n[4 upvotes] Following\n\n[3 upvotes] Yep, biggest thing missing from Codex at the moment, they have a cloud version but it’s restricted to 5.5. Doesn’t seem nearly as powerful as Claude either can’t even push to GitHub while Claude can even deploy my build scripts. ",
  "transcript_chars": 3172,
  "ingested_at": "2026-07-14T01:30:09.526440+00:00",
  "source": "reddit",
  "yt_meta": {
    "score": 70,
    "upvote_ratio": 0.93,
    "num_comments": 38,
    "author": "invocation02",
    "is_self": true
  }
}