Execution & permissions

Autonomous work needs explicit boundaries. The engine’s approach is to put those boundaries in the execution path.

Tool actions

Shell commands, file writes, and network access are distinct kinds of action. Configure the permissions appropriate to each workload instead of treating all tool calls as equivalent.

Policy decisions

Policy can allow, ask, or deny an action. Approval is part of the execution model; a permitted action does not necessarily require a new dialog each time.

Network and models

Outbound access is denied by default in the documented security model. Model connectivity and remote execution require deliberate configuration. Review the current implementation and deployment instructions for the revision you run.

Evaluate your deployment

Inspect tool permissions, working directories, model endpoints, and execution records before running a workload. See Trust for our operational principles.