Security and policy
Security and policy
Permissions, content exclusion, hooks, sandboxing, and persistent policy/configuration state.
How this volume fits
flowchart TD Policy[Settings/policy state] --> Permissions[Permission system] Permissions --> Sandbox[Sandboxing] Permissions --> Hooks[Hooks] Policy --> Content[Content exclusion/redaction] Hooks --> PermissionsPages
| Page | Why read it | File |
|---|---|---|
| Permission system design in Copilot CLI | Central PermissionService pipeline, rule precedence, path/URL managers, prompts, scopes, and allow-all behavior. | permission-system-design.md |
| Content exclusion and redaction | Content-exclusion service, policy fetch/merge, filtered outputs, bypass limits, secret env vars, and redaction. | content-exclusion-and-redaction.md |
| Hooks and lifecycle automation | Hook schema, command/HTTP hooks, VS Code aliases, security restrictions, events, and lifecycle automation. | hooks-lifecycle-automation.md |
| Sandbox Implementation | Local command sandboxing, /sandbox, SANDBOX gate, shell wiring, MXC policy, and platform caveats. | sandboxing.md |
| Settings and configuration persistence | Config roots, typed stores, writeKey/load paths, settings overlays, URL/MCP/plugin/sandbox state, and migration. | settings-config-persistence.md |
Reading guidance
- Permissions are the central policy layer.
- Content exclusion, hooks, sandboxing, and settings are cross-cutting safeguards.