Offload: Speed up the agent loop by running tests remotely
nvader
12 points
2 comments
March 19, 2026
Related Discussions
Found 5 related stories in 80.0ms across 8,303 title embeddings via pgvector HNSW
- How Offload Works: Inside the Rust CLI that sped up our tests by 6x thejash · 12 pts · April 07, 2026 · 71% similar
- Docker Offload redbell · 22 pts · April 05, 2026 · 58% similar
- Android CLI: Build Android apps 3x faster using any agent ingve · 186 pts · April 16, 2026 · 52% similar
- Agents that run while I sleep aray07 · 288 pts · March 10, 2026 · 51% similar
- Open-Source Agentic QA Harness with Memory pranshuchittora · 50 pts · May 19, 2026 · 51% similar
Discussion Highlights (2 comments)
bfogelman
we’ve been using it internally (on sculptor) and the speed ups are crazy — we can now have our agents run tests all the time and iterate quickly! Excited other people can now give it a spin
nvader
I'm one of the devs of Offload here, happy to answer any questions. We built Offload because parallel coding agents exposed a bottleneck we hadn't fully felt before: agents write fast now, but our integration suite (345 Playwright tests) were still taking 12 minutes per run. There’s only so much parallelism you could get out of a single laptop, and our agents were spending more and more time running and waiting for tests. Offload is a Rust CLI, and agents invoke it directly to spin up isolated Modal sandboxes and distribute tests to them. The results are merged back and returned to your agent. The integration test suite for Sculptor makes heavy use of Playwright, and we saw the time for a run drop from ~726s to ~120 (More than a 6x speedup!) We've deliberately chosen a pluggable architecture so that we can operate with almost any test framework. We ship with support for pytest, vitest and cargo-nextest out of the box. We take a similar approach to support any bash-scriptable sandbox provider, but we’re launching with support for Modal to start. There are some caveats to share: suites under 2 minutes won't see meaningful gains since the overhead of preparing the testing image and sharing out the sandboxes is going to dominate. Short-running unit tests at high volume also get less scheduling efficiency from LPT. We're looking at work-stealing as a next step there. We'd love to hear any feedback! Install with `cargo install offload`, and the code is at github.com/imbue-ai/offload