Cloud execution

Start with Cloud execution. With active Workspace access and available usage, Agents can run Task and Chat work without connecting your computer. Choose Local execution later when the work needs tools, credentials, or files on a computer you control.

Cloud execution is available without a machine

Cloud execution is part of every operational Workspace access contract, not a separately purchased worker product. Task Machine provisions a temporary, isolated environment for each Cloud Run and removes that compute when execution ends. Files that a Task or Chat may need again are stored separately from the temporary environment.

You do not choose infrastructure sizes or buy individual worker slots.

Automatic capacity starts at ten Tasks with active Cloud Runs, twenty Cloud Runs, and ten Scheduled Runs. Task Machine can increase those limits when available purchased or complimentary usage and ready work support more parallel execution.

Several Cloud Runs for one Task share that Task's active Task slot, while the separate Cloud Runs limit counts each Run. Chat Runs use their own lane, and Local Runs do not claim Cloud Task capacity. Check Limits for your workspace's current values.

When the current limit is occupied, additional work waits visibly until capacity becomes available. A scheduled Task whose start time has passed remains ready and can show that it is late. Task Machine does not interrupt healthy work already running to make room.

The Limits page shows Cloud, Local, Scheduled, and Chat Run capacity, with live counts as work starts, queues, and finishes. Workspace managers may request a higher limit for review, but submitting a request does not itself change capacity or promise approval.

Cloud files have a separate retention period

Files used by a started Task or Chat Cloud Run normally remain available for 60 days after the latest Run so later work can continue from the same place. Running the Task or continuing the Chat extends the date.

Marking a Task Done or Cancelled, or archiving it, instead schedules its Cloud files for deletion after 24 hours unless you reopen or restore the Task first.

When all startup attempts fail before any Run starts with newly created files, Task Machine removes them only after the Cloud provider confirms that no temporary environment still has them attached. Files used by an earlier started Run keep their normal retention.

Retained storage is charged in complete rolling 24-hour periods in advance while those files remain available. The first period remains charged even when a Run never starts and the files are deleted before that day ends.

At the applicable deletion deadline, Task Machine removes the Cloud files while preserving the Task or Chat, transcript, comments, receipts, and separately saved results.

For work that needs a connected computer, read Local execution. Workspace pricing and access explains the fixed startup and shutdown periods, active runtime, retained-file storage, access contracts, and monthly usage.