Show HN: Rig – Open-source cloud desktops for AI agents
Rig gives each coding agent a Linux desktop in the cloud with your code, a running dev server, tests and a signed-in Chrome, so your laptop stays fast and you can run many agents at once. Watch the 45-second demo (with sound) Setup · Logins · Repos · Saved desktops · Computer use · Quick start · Manage · Security · FAQ · Docs Claude Code, Cursor or Codex keeps editing code on your laptop. The heavy work runs in its cloud desktop, which sleeps when nobody uses it and wakes in about two seconds.
- ▪Rig gives each coding agent a Linux desktop in the cloud with your code, a running dev server, tests and a signed-in Chrome, so your laptop stays fast and you can run many agents at once.
- ▪Watch the 45-second demo (with sound) Setup · Logins · Repos · Saved desktops · Computer use · Quick start · Manage · Security · FAQ · Docs Claude Code, Cursor or Codex keeps editing code on your laptop.
- ▪The heavy work runs in its cloud desktop, which sleeps when nobody uses it and wakes in about two seconds.
3 outlets in our directory ran this story, first to last over 26 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Ideas on modernizing the open-source desktop — LWN.net
- ▪ [$] Ideas on modernizing the open-source desktop — LWN.net (Linux Weekly News)
Hacker News (AI / LLM) files mainly under ai. We currently carry 6,346 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/ShadowWalker2014/rig |
| Publication time | Thu, 24 Sep 2026 18:01:51 +0000 |
| Retrieval time | 2026-09-24T18:05:26.788Z |
| Last seen | 2026-09-24T18:05:26.788Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | CgSStCB9xP7O · 4 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Rig gives each coding agent a Linux desktop in the cloud with your code, a running dev server, tests and a signed-in Chrome, so your laptop stays fast and you can run many agents at once. Watch the 45-second demo (with sound) Setup · Logins · Repos · Saved desktops · Computer use · Quick start · Manage · Security · FAQ · Docs Claude Code, Cursor or Codex keeps editing code on your laptop. The heavy work runs in its cloud desktop, which sleeps when nobody uses it and wakes in about two seconds. Why Rig One coding agent barely uses your laptop. What freezes it is everything around the agent: a dev server per branch, a Chrome for checking the UI, and test runs. Two or three tasks in, a 16 to 24 GB laptop starts swapping. Rig moves that work into one cloud desktop per branch.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.