Loading video...

Video Failed to Load

Go Home

Your parallel agents needed scalable test coverage yesterday Introducing Offload: a Rust CLI that spreads your test suite across 200+ Modal sandboxes, freeing your CPU to keep your agents shipping. On our Playwright suite, it took a 12 min run to 2, at $0.08 a run

102,032 views • 7 months ago •via X (Twitter)

18 Comments

Imbue's profile picture
Imbue7 months ago

Open-source (of course). Drop-in for pytest, cargo-nextest, vitest. One TOML config. Try it on your agents

Imbue's profile picture
Imbue7 months ago

Offload continues our march to better, open software that benefits people like you. At Imbue, we believe open agents are foundational. See more of our work @GitHub

Kanjun 🐙's profile picture
Kanjun 🐙7 months ago

@modal Thank god for Offload, some of our test suites were badly slowing down the agent iteration cycle 😭

FileCity's profile picture
FileCity7 months ago

@modal Made a File City Tour of Offload A visual map + narrated walkthrough of the open-source Rust CLI that spreads test suites across 200+ @Modal sandboxes for ultra-fast parallel testing Great work! @imbue_ai

Daniel Mewes 🦋 @dmewes com's profile picture
Daniel Mewes 🦋 @dmewes com7 months ago

@modal Congrats to the Offload team for shipping this! It took a lot of ingenuity to get it run this fast.

Ehsan Nour's profile picture
Ehsan Nour7 months ago

@modal can't believe how quickly we are launching new products 😮

Lauren Dash's profile picture
Lauren Dash7 months ago

@modal can’t keep up with all the product launches! way to go @404Cause

Millan Philipose's profile picture
Millan Philipose7 months ago

@modal @grok is this true

Nikhil Kulkarni's profile picture
Nikhil Kulkarni7 months ago

@modal Speed your tests up, free your CPU, keep shipping 😎

Ashley Slocum's profile picture
Ashley Slocum7 months ago

@modal congrats to the Offload team!!

Millan Philipose's profile picture
Millan Philipose7 months ago

@modal This thing is absurdly fast

Oliver's profile picture
Oliver7 months ago

@modal super fascinating. Is it cloning the repo to every sandbox through the docker image?

Cindy Wei's profile picture
Cindy Wei7 months ago

@modal The parallelized speed is so impressive! I'm curious about optimizations around parallel agents, how often they should run self-tests to check if they're on the right track and if the entire test suite needs to be rerun each time.

Imbue's profile picture
Imbue7 months ago

@cinxinwei @modal Offload exists to pass that decision along to you as the developer. In the past, integration tests on large projects took too long for agents to run them meaningfully often. We're still working internally to calibrate how often we run our integration tests in the agent's loop!

Catherine Kim's profile picture
Catherine Kim7 months ago

@modal LOVE how fast it makes tests run

Adam Crabtree's profile picture
Adam Crabtree7 months ago

@modal Incredible.

Karolis's profile picture
Karolis7 months ago

@modal That’s quite expensive 😀

ً's profile picture
ً7 months ago

@modal @grok whats this?

Related Videos

#1 skill for developers in 2026: Automate everything you can using AI. I bet my lunch your team is dealing with all of these: • Stale documentation • Outdated dependencies • Poor test coverage • Deprecated APIs Every company I work with has these same problems. You can solve all of these right now. Automatically. Using AI. Here are 3 examples. Watch the attached video: I'm using Ona Automations to tackle this. These are background agents that run in the cloud, in a fully configured dev environment with your toolchain, your dependencies, and your services. You can run an unlimited number of these agents in parallel and across all your repositories. Claude Code and Codex only run locally, so they are hard to scale, and you can't run them when your computer is closed. Ona runs in the cloud. Here are the three examples: 1. Test coverage Run a nightly automation to identify any untested code paths, generate candidate tests, verify they pass, and open draft PRs. You wake up every morning to PRs that improve your test coverage. 2. Dependency upgrades Configure a weekly automation that bumps a dependency version, runs your full test suite, and reports any regressions. If everything is clean, it opens a PR. If something breaks, it opens a report so you can decide what to do. 3. Documentation auditing Set up a weekly automation that checks recent commits against your README file and setup guides, identifies broken examples and outdated instructions, and opens a PR with fixes.

Santiago

25,804 views • 8 months ago