Skip to main content
Orgo automatically stops computers that have been idle — no active VNC connections, API calls, or network traffic — for a configurable period. This keeps costs low and frees up resources.

​
How it works

Orgo monitors network activity on each computer every few seconds. When no traffic is detected for the configured duration, the computer is suspended. Its full state (desktop, files, running processes) is preserved and it can be restarted instantly. Activity that resets the idle timer:
  • API calls (screenshots, clicks, typing, bash commands)
  • VNC/browser connections
  • Any network traffic to the computer
Activity that does NOT reset the timer:
  • Processes running inside the computer (CPU-bound work with no external connections)

​
Default behavior

PlanAuto-stopConfigurable
Free15 minutesNo
DeveloperDisabledYes
StartupDisabledYes
MaxDisabledYes
EnterpriseDisabledYes
Free-tier computers always auto-stop after 15 minutes of inactivity. This is not configurable. Paid plans have auto-stop disabled by default. You can enable it per-computer at creation time to optimize costs.

​
Configuring auto-stop

Pass auto_stop_minutes when creating a computer: 
# Auto-stop after 30 minutes of inactivity
curl -X POST https://www.orgo.ai/api/computers \
  -H "Authorization: Bearer $ORGO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workspace_id": "550e8400-e29b-41d4-a716-446655440000",
    "name": "agent-1",
    "auto_stop_minutes": 30
  }'
Set auto_stop_minutes to 0 to explicitly disable auto-stop (paid plans only).

​
Restarting auto-stopped computers

When a computer is auto-stopped, restart it with: 
curl -X POST https://www.orgo.ai/api/computers/{id}/start \
  -H "Authorization: Bearer $ORGO_API_KEY"
The computer restores to its previous state and becomes accessible within moments. The idle timer resets when the computer starts.

​
Best practices

Long-running agents

Set auto_stop_minutes: 0 for agents that need to stay alive between tasks.

On-demand agents

Set auto_stop_minutes: 15 or 30 for agents that run periodically. They auto-stop between jobs and restart on demand.

Development

Use a longer timeout like auto_stop_minutes: 60 during active development so your computer doesn’t stop while you’re thinking.

Cost optimization

Enable auto-stop on all non-critical computers. Stopped computers don’t incur compute charges.