Check disk use. Clean up finished tasks.

See project, container and session disk sizes. Stop empty development containers after a configurable grace period while retaining their workspaces. Review declared artifacts and remove ready task leftovers before an agent exits. Server policies also clean old unused images and temporary CI database volumes while clients are closed. Active sessions and retained data stay protected.

How it works

  1. Review declared leftovers

    Inspect declared task artifacts and managed disk usage before cleanup. Undeclared files are not automatically attributed to a task.

  2. Set the empty-container grace period

    Settings → Idle containers controls your server-side policy. Active sessions and native processes prevent shutdown; working files and native conversations remain retained.

  3. Inspect lifecycle history

    Inspect why an empty container waits, stays running or stops. Queued commands, confirmed host outcomes and unconfirmed results remain separate; retained work stays available.

  4. Clean up ⁠Docker storage by workspace

    Settings → Cleanup → ⁠Docker storage lists each Host’s volumes, images, build cache and stopped containers by Project and workspace, largest first. Clean up a stopped workspace while keeping its volumes and session files; the Host rechecks every item before removal, and nothing is removed automatically by default. Workspace cleanup has not yet run against live workspace data.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

Watch the workflow

HostsREAL UI

Loading the recorded terminal…

Walkthrough paused

Release videos

YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.