Skip to content

Configuration, Permissions and Sandboxing

Model and reasoning configuration should match task complexity, latency and cost. Easy, bounded edits may not need the most expensive setting.

A sandbox is an execution boundary that restricts file, process or network access. It reduces blast radius but does not replace secure review. Approval policy governs which actions require human consent; high-impact, external, destructive or credential-sensitive actions deserve tighter approval.

MCP integrations expose external tools and resources. Each integration still needs scoped credentials, clear tool contracts and safe defaults. Secrets should come from managed mechanisms, not prompts or committed files.