Render removes the runtime limit on its AI agent sandboxes

Render’s AI Sandboxes, now in public beta, no longer have to end after a fixed runtime. A sandbox’s timeout can be set as high as 30 days or disabled entirely, so an agent on a multi-day job, such as a codebase migration, can keep its running process, memory and open files the whole time.

By default, a sandbox that sits idle for 15 minutes is automatically snapshotted and suspended, then wakes back up on the next command, typically in under a second and up to 3 to 10 times faster when restored from a snapshot. That idle timeout is configurable up to 24 hours, or can be disabled too. You pay for CPU and memory only while a sandbox is actively running, not while it’s suspended, just for its snapshot storage. Each sandbox gets 40GB of writable storage, and the feature is available on all workspace plans, currently limited to Render’s Oregon region.

Why it matters: if you’re running coding agents or other long jobs on Render, you no longer need to checkpoint state yourself to survive a forced restart, and you stop paying for idle compute between agent turns. It ships alongside Render’s separate Workflows service for retrying failed multi-step jobs and a Shared Filesystems feature for sharing files across sandboxes.

The caveat: this is a public beta, limited to one region, and Render says the limits may still change.