cloudroom
Open-source, self-hostable Rust runtime that runs Claude Code, Codex, and Pi in the cloud.
Runs with mockssource: GitHubTypeScriptApache-2.0commit 63b335db4055
TypeScript, Apache-2.0 licensed. The project labels itself: ai agents, background agents, claude code, cloud agents, codex, coding agents, rust and self hosted.
cloudroom runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Rust core (cloudroom v0.1.84) builds from source on Ubuntu 24.04, passes all 49 tests (24 unit + 25 integration), passes clippy with no warnings, is correctly formatted, and the compiled binary reports its version. The desktop GUI (gui/) could not be built because it requires Node 22.19+ and pnpm 9.15.9, but only Node 18.19.1 is available in the container.
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 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
- runtime integration test harness_commits_drop_ai_co_authors_and_keep_human_ones failed — the Git config-based hook mechanism (hook.<name>.command/hook.<name>.event via GIT_CONFIG_COUNT env vars) is not supported by Git 2.43.0 on Ubuntu 24.04, so the prepare-commit-msg/commit-msg hooks never fired and commit messages were not filtered20 minutes
- Two observability unit tests failed: private_stderr_rotation_counts_encoded_bytes_and_keeps_two_private_files and api_outage_keeps_local_diagnostics_and_overload_is_visible — both caused by Rust's fs::create_dir creating temp dirs with mode 0o775 (umask 0002), which the write_stderr security check rejects because m.mode() & 0o022 != 012 minutes
- Install time
- 7 minutes
- Cold machine to finish
- 29 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- cargo test --locked --all-targets: 24 unit tests passed, 5 adapter integration tests passed, 3 journal tests passed, 14 runtime integration tests passed, 1 storage test passed, 2 terminal tests passed; cargo fmt --check: no diff; cargo clippy --locked --all-targets -- -D warnings: 0 warnings; binary at ./target/release/cloudroom --version prints 'cloudroom 0.1.84 (63b335db4055)'
- Model tokens used
- 876,368
- Exact commit tested
- 63b335db4055
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- Core build (release): ~1m 44s - Core tests + format + clippy: ~3m total - Total: well under 90 minutes Now let me produce the final result. tokens used 876,368 Let me calculate approximate install time: - Rust installation via rustup: ~9s - Core build (release): ~1m 44s - Core tests + format + clippy: ~3m total - Total: well under 90 minutes Now let me produce the final result.
Replay 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
- Installed in 7 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 106 ai-agents projects Argusic has installed and timed, cloudroom was the 51st fastest to reach a running state, and 78 of 106 reached one at all.
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 | 1/3 | Runs with mocks | 92.00 | 0.31 |
Topics (from GitHub)
ai-agentsbackground-agentsclaude-codecloud-agentscodexcoding-agentsrustself-hosted
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/cloudroom)Questions
- Does cloudroom run?
- cloudroom runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test cloudroom?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 63b335db4055. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test cloudroom?
- The run that produced this verdict cost $0.31: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does cloudroom take to install?
- 7 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 need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing cloudroom?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does cloudroom compare with the alternatives?
- Of the 106 ai-agents projects Argusic has installed and timed, cloudroom was the 51st fastest to reach a running state, and 78 of 106 reached one at all.
- Where is the evidence for cloudroom?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.