Environment isolation
Each Automation runs in an isolated environment with dedicated resources. No access to other Automations or user environments. See Environments.Command deny lists
Prevent Automations from executing dangerous commands (sudo, rm -rf /, cloud CLIs). Blocked commands fail immediately. Configure at the organization level.
See Command deny lists.
Executable deny list
Block specific binaries from running inside Automation environments using kernel-level enforcement. Unlike command deny lists, executables are identified by content hash and cannot be bypassed by renaming. See Executable deny list.Audit logging
Every execution is logged: commands, file changes, PRs created, errors. Use for debugging and compliance. See Audit logs.Concurrency limits
Control parallel execution to manage costs and prevent Automations from running excessively. Maximum values depend on your plan.
Core plans enforce the caps listed above. Enterprise plans are unrestricted by tiering but are subject to the current system-wide ceiling of 25 concurrent and 100 total actions per Automation. Contact sales if you need higher limits.
Setting values above your plan’s cap returns an error. Existing Automations are not retroactively affected. Only new creates and updates are validated.