cloudroom-core
Cloud agents for any harness. Claude Code, Codex, Pi, and OpenCode run in isolated sandboxes, and live sessions move between your Mac and the cloud.
Runssource: GitHubhomepageTypeScriptApache-2.0commit e760393ec748
TypeScript, Apache-2.0 licensed. The project labels itself: ai agents, background agents, claude, claude code, claude code cli, cloud agents, cloudroom and codex.
cloudroom-core runs. An Argusic agent installed it in 32 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Cloudroom core built from source, passes fmt/clippy and all 31 Rust unit/integration tests, boots as a real HTTP service on loopback, and completed an authenticated session (start, prompt, recorded history, graceful restart/resume) against a local PostgreSQL 16 mock with both schema migrations applied.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- No Docker/postgresql service to run the repo's own core_e2e/foundation suite14 minutes
- core_fixture IPv6 subtest fails: '[::1]:0' bind returns EADDRNOTAVAIL (no IPv6 in container)10 minutes
- cargo test --locked --all-targets failed: 2 observability tests panic (unsafe diagnostic directory) under container umask 00028 minutes
- No cargo/rustc in container (README requires Rust 1.89+)4 minutes
- Install time
- 32 minutes
- Cold machine to finish
- 33 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- cargo test --locked --all-targets (umask 022) exited 0, 31 passed; curl -H 'Authorization: Bearer <token>' http://127.0.0.1:<port>/v1/health returned 200 and no token returned 401; POST /v1/sessions -> 202, prompt receipt completed, 58 history rows for cr_demo in mock PostgreSQL; restart resumed and completed follow-up; shutdown exit 0
- Model tokens used
- 3,379,931
- Exact commit tested
- e760393ec748
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
import json
d = json.load(open('/tmp/result.json'))
line = 'ARGUSIC_RESULT:' + json.dumps(d, separators=(',', ':'))
print(line)
assert ' ' not in line.split(':',1)[1][:1] # single line
with open('/tmp/result-line.txt','w') as f: f.write(line+'\\n')
PY
wc -c /tmp/result-line.txt" in /work/repo
succeeded in 0ms:
2301 /tmp/result-line.txt
tokens used
3,379,931Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 32 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.
Of the 124 ai-agents projects Argusic has installed and timed, cloudroom-core was the 114th fastest to reach a running state, and 96 of 124 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.10 | |
| Argusic Runner | 1/3 | Runs | 100.00 | 0.23 |
Topics (from GitHub)
ai-agentsbackground-agentsclaudeclaude-codeclaude-code-clicloud-agentscloudroomcodexcodex-clicoding-agentscursorhermes-agentompopencodepirustself-hosted
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cloudroom-core)Questions
- Does cloudroom-core run?
- Yes. cloudroom-core runs. Argusic installed and launched it on a clean machine in 32 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test cloudroom-core?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit e760393ec748. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test cloudroom-core?
- The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cloudroom-core take to install?
- 32 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does cloudroom-core need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cloudroom-core?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does cloudroom-core compare with the alternatives?
- Of the 124 ai-agents projects Argusic has installed and timed, cloudroom-core was the 114th fastest to reach a running state, and 96 of 124 reached one at all.
- Where is the evidence for cloudroom-core?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.