[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-93348":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":16,"stars30d":16,"stars90d":15,"forks30d":15,"starsTrendScore":15,"compositeScore":17,"rankGlobal":10,"rankLanguage":10,"license":18,"archived":19,"fork":19,"defaultBranch":20,"hasWiki":21,"hasPages":19,"topics":22,"createdAt":10,"pushedAt":10,"updatedAt":33,"readmeContent":34,"aiSummary":35,"trendingCount":15,"starSnapshotCount":15,"syncStatus":36,"lastSyncTime":37,"discoverSource":38},93348,"blitzos","blitzdotdev\u002Fblitzos","blitzdotdev","BlitzOS allows cloud agents to boot already knowing your work, and keep working with your laptop closed","https:\u002F\u002Fblitzos.com",null,"JavaScript",128,14,1,0,12,50.73,"MIT License",false,"main",true,[23,24,25,26,27,28,29,30,31,32],"agentic","ai-agents","claude","claude-code","claude-md","cloud","codex","codex-skill","developer-tools","warm-start","2026-07-22 04:02:08","\u003Cdiv align=\"center\">\n  \u003Ch1>BlitzOS\u003C\u002Fh1>\n  \u003Cp>\u003Cb>Run Claude Code in the cloud with full context of your work (go close your laptop!)\u003C\u002Fb>\u003C\u002Fp>\n\n  [![Website](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fblitzos.com-website-black)](https:\u002F\u002Fblitzos.com)\n  [![Discord](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FDiscord-join-5865F2?logo=discord&logoColor=white)](https:\u002F\u002Fdiscord.gg\u002Fv3vQdAgPq6)\n  [![License](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-MIT-blue)](LICENSE)\n\u003C\u002Fdiv>\n\n## What is this?\n\nYour Claude subscription includes free cloud computers. Every cloud agent you start at [claude.ai\u002Fcode](https:\u002F\u002Fclaude.ai\u002Fcode) gets a fresh VM that keeps working after you close your laptop.\n\nThe problem: **every new VM boots knowing nothing.** It doesn't know which repos belong together, how they relate, what your conventions are, or what the last agent did. \n\nBlitzOS fixes the problem by building you a **context repo**: one private GitHub repo owned by you that teaches every new cloud agent your whole setup:\n\n```\nyour-context-repo\u002F\n  CLAUDE.md      # the map: your repos, how they relate, conventions, work loop\n  .gitmodules    # member repos pinned by reference: no code is ever copied in\n  sessions\u002F      # every cloud agent commits a record of what it did\n  docs\u002F          # optional power-mode setup\n```\n\nLaunching a cloud agent that can do real work becomes one click: the VM boots with the context repo plus every work repo auto-selected. Cloud agents read CLAUDE.md, read what previous cloud agents did, and start working with no blockers. Your laptop can be off the entire time.\n\n## Quickstart\n\n**Browser (fastest):** sign in with GitHub at [blitzos.com](https:\u002F\u002Fblitzos.com), pick the repos that belong together, and BlitzOS creates the context repo and gives you one-click launches, plus a feed that tracks every cloud agent's live status.\n\n**Local (most private):** this skill builds everything on your machine and grants nothing to BlitzOS servers.\n\n**Self-host (yours end to end):** run the same portal on your own Cloudflare account — your OAuth app, your database, your domain. One script, about 10 minutes: [portal\u002FSELF-HOSTING.md](portal\u002FSELF-HOSTING.md).\n\nNeeds Claude Code, Git, `gh` (authenticated), `jq`, and Node 18+.\n\n```sh\ngit clone https:\u002F\u002Fgithub.com\u002Fblitzdotdev\u002Fblitzos.git\ncd blitzos && .\u002Finstall.sh\nclaude \"set up blitzos\"\n```\n\n## Managed BlitzOS\n\nContext repository, but for your whole company. Give cloud agents a role and launch them with scoped context, your team's tools (Google Workspace, Slack, Linear, Stripe, etc), and credentials. Agents become as capable as your coworkers. \n\nWhat you get: \n- **Roles, not setups** — give a cloud agent a role and launch: it gets the company repo (code, plans, research, docs, goals), your team's tools (Google Workspace, Slack, Linear, analytics, Stripe, etc) and the credentials that role needs.\n- **Whole loops, not just code** — read the support ticket, check the code, ship the fix, reply to the customer, close the ticket from one cloud agent, start to finish.\n- **Policy layer over capability and credentials** — every grant is per role and per agent, never account-wide; each cloud agent is a fork of your company holding only what its job needs.\n- **Audit trail end to end** — everything every agent touched, when, and with which credential.\n- **Runs where you need it** — our managed infrastructure or your own VPC.\n\n[Join the waitlist](https:\u002F\u002Fblitzos.com\u002Fwaitlist)\n\n## What you get\n\n- **One-click launch** a link that selects the context repo and every member repo, in the right order, every time.\n- **Warm multi-repo context** cloud agents start knowing your conventions, the repo map, and what previous agents did.\n- **Native repository access** Claude reads, writes, pushes branches, and opens PRs on every selected repo through Anthropic's own GitHub rail. Zero tokens in the default path.\n- **A cloud agent feed** [blitzos.com](https:\u002F\u002Fblitzos.com) shows every cloud agent's live status (working \u002F quiet \u002F done) with a link to open any of them, from any device. One 2-minute environment setup.\n- **Your connectors** cloud agents can use Linear, Slack, Gmail, and whatever else is already connected to your claude.ai account.\n- **A shared work log** each cloud agent records PRs and decisions in `sessions\u002F`, so work compounds instead of evaporating.\n\n## Security model\n\nThe default flow needs **zero credentials**. The launch link selects the context repo and every member repo through Anthropic's native GitHub proxy, so all repository access stays on Claude's own rail. Your source code is never copied into the context repo (members are pinned by reference) and never touches BlitzOS servers.\n\n## Vision & roadmap\n\n**Your agent setup should live in a repo, not on a machine.**\n\nLocal Claude Code is powerful because your machine accumulates state: checkouts, skills, config, memory. That's also the trap: the state is stuck in one laptop. BlitzOS moves it into git, where it's versioned, reviewable, and portable. Once your context, your skills, and your work log live in a repo, a fresh cloud VM isn't a downgrade from your laptop — it's your setup, available in unlimited copies, from anywhere, in parallel, and always current. The durable unit of agentic work stops being the machine or the cloud agent. It's the context repo.\n\nShipped:\n\n- [x] **Context repos** — map + pinned member repos + sessions log, generated in one command\n- [x] **One-click multi-repo launch** — zero tokens, native GitHub rail\n- [x] **Live cloud agent feed** — cloud agents report status to blitzos.com; see working \u002F quiet \u002F done and open any cloud agent from any device\n\nShipping now:\n\n- [ ] **Clean-prompt status** — cloud agents connect to the feed through a one-time environment key; nothing gets appended to your prompt\n- [ ] **Guided setup** — the feed walks you through the 2-minute environment config and verifies it live\n\nNext:\n\n- [ ] **Steer from the feed** — reply to a running cloud agent from blitzos.com; the last reason to keep a terminal open goes away\n- [ ] **Skills travel with the repo** — put your skills in the context repo and every VM boots with them: your `~\u002F.claude`, versioned and portable\n- [ ] **Self-updating context** — cloud agents propose PRs back to the context repo when they learn something (a new convention, a decision, a map change), so context compounds instead of rotting\n- [ ] **Codex support** — the same context repo boots OpenAI Codex cloud agents; your context stops being vendor-locked\n\n## Troubleshooting\n\nIf a repo is missing in the default flow, confirm the Claude GitHub App can access that repository, then reopen the generated launch link. In power mode, follow the generated `docs\u002FCLOUD-SETUP.md` for token setup and rotation.\n\n## License\n\nMIT. See [LICENSE](LICENSE).\n","BlitzOS 是一个为 Claude Code 云代理提供持久化工作上下文的开源工具。它通过构建私有 GitHub 上下文仓库（含 CLAUDE.md 配置、git submodules 关联代码库、会话记录等），使每次启动的云代理自动继承用户项目结构、开发约定和历史操作，实现“合盖即续工”。支持浏览器一键部署、本地运行与自托管三种模式，依赖 GitHub OAuth、Claude Code 订阅及基础 CLI 工具链。适用于需要长期维护多仓库协作上下文、提升云代理任务连贯性与自主性的开发者及技术团队。",2,"2026-07-17 02:30:03","CREATED_QUERY"]