Permissions cheat sheet

Kiro CLI v3 capability rules. Source: kiro.dev/docs/permissions.

Rule anatomy

rules:
  - capability: shell        # what kind of operation
    match: ["npm *"]         # glob(s)
    exclude: ["npm publish*"]# must NOT match
    effect: allow            # deny | ask | allow | evaluate

Where rules live

ScopeLocation
user~/.kiro/settings/permissions.yaml
workspace~/.kiro/workspace-roots/<hash>/permissions.yaml (outside the repo)
agentpermissions field in the agent profile
sessionIn memory (from approval prompts)
Resolution

deny > ask > allow > evaluate. No scope precedence; most restrictive wins.

v2 to v3 map

v2v3
allowedCommands / deniedCommands (regex)shell match (glob), allow / deny
denyByDefault: trueshell exclude list with deny
allowedPaths / deniedPathsfs_read / fs_write match
allowedTools, /tools trustrules; session-wide: --trust-all-tools or /tools trust-all
use_awsRemoved; use an AWS MCP server or shell rules
Headless narrow trust--no-interactive --trust-tools=read_file,grep_search (exact tool IDs)

Glob rules

CapabilitySyntax
fs_read, fs_write* within a component, ** across, {a,b}, [abc]; no-wildcard path matches children
shell, web, mcp* only (any characters)

Useful commands

/permissions                 # view and change policies (incl. Approve for me)
/upgrade-agent               # convert v2 agents; backs up originals
/upgrade-agent diagnostics   # conversion warnings
kiro-cli agent validate --path .kiro/agents/my-agent.json