kiro-cli Docker isolation issue (on aws mac)

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 26.4.0 (25E246)

### Expected behaviour

Kiro-CLI runs on the local Mac, executes tasks, and writes output files directly to specified local folders (e.g., ~/, ~/projects/) as it had been
doing for the past week without issue.

### Actual behaviour

After the kiro-CLI auto-update on April 13–14, 2026, the tool runs and processes tasks normally but silently fails to write output files to local Mac
folders. File writes are blocked by the Ava Reveal DLP (Data Loss Prevention) agent, which re-evaluated kiro-CLI as a newly seen binary after the
update and applied a restrictive write policy.

Impact

All tool output is lost — work completes inside kiro-CLI but no files are saved to disk.

The investigation already found strong evidence pointing to your corporate security solution. Here's a clear breakdown:

Root Cause: Ava Reveal DLP Agent (Data Loss Prevention)

What Was Found

1. Kiro-CLI was updated April 13-14, 2026 — right before the problem started:
- /Applications/Kiro CLI.app/Contents/MacOS/kiro-cli — updated Apr 13, 17:00
- ~/Library/Application Support/kiro-cli/bun — updated Apr 14, 20:43
- Symlink ~/.local/bin/kiro-cli — recreated Apr 14, 20:37

2. Ava Reveal DLP Agent is actively running on your Mac:
- Installed at /Library/SystemExtensions/
- The kiro-cli binary itself has DLP tracking metadata attributes:
- com.nextdlp.reveal.agent.file-id.0
- com.nextdlp.reveal.agent.file-source-path.0
- Active helper: ~/Library/Preferences/uk.ava.reveal.Reveal-Agent-Helper.plist

3. Docker is NOT the cause — Docker Desktop is installed but the daemon is not running. This is not a container isolation issue.

---
Why It Broke After the Update

The kiro-cli update likely triggered a DLP policy re-evaluation. When the binary hash/signature changed, the Ava agent treated it as a newly seen
application and applied a restrictive default policy — blocking file writes to arbitrary local paths to prevent data exfiltration.

---
How to Fix It

Option 1 — Ask your IT/Security team (recommended):
- Ask them to whitelist kiro-cli in the Ava Reveal DLP policy
- Specifically: allow file writes to your working directories (e.g., ~/, ~/projects/)
- Reference the binary: /Applications/Kiro CLI.app/ signed by Amazon (Team ID: 94KV3E626L)

Option 2 — Test a workaround yourself:
Try writing to /tmp/ first to confirm DLP is the blocker:
# If kiro-cli can write to /tmp but not ~/ — DLP is confirmed
kiro --output /tmp/test-output.txt

Option 3 — Check DLP logs (may need admin):
ls /Library/Application\ Support/uk.ava.reveal.agent.sysmon/

Option 4 — Check extended attributes on the binary:
xattr -l /Applications/Kiro\ CLI.app/Contents/MacOS/kiro-cli
If you see the com.nextdlp.reveal.* attributes, DLP is confirmed as tracking it.

---
Summary

┌───────────────┬────────────────────────────────────────────────────────┐
│ Factor │ Detail │
├───────────────┼────────────────────────────────────────────────────────┤
│ Root cause │ Ava Reveal DLP Agent blocking file writes │
├───────────────┼────────────────────────────────────────────────────────┤
│ Trigger │ Kiro-CLI v2.0.0 update (Apr 13-14) changed binary hash │
├───────────────┼────────────────────────────────────────────────────────┤
│ Not the cause │ Docker (daemon is stopped) │
├───────────────┼────────────────────────────────────────────────────────┤
│ Fix │ IT team whitelist of kiro-cli binary in DLP policy │
└───────────────┴────────────────────────────────────────────────────────┘

### Steps to reproduce

none

### Environment

```yaml

[q-details]
version = "2.0.0"
hash = "0026b0505ef7bc2b10780c7bdb57813e5d949747"
date = "2026-04-13T09:10:32.211225Z (2d ago)"
variant = "full"

[system-info]
os = "macOS 26.4.0 (25E246)"
chip = "Apple M3 Pro"
total-cores = 11
memory = "18.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "macOS"
install-method = "brew"

[env-vars]
PATH = "/Users/USER/.toolbox/bin:/Users/USER/.local/bin:/Users/USER/Library/Python/3.9/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/opt/pkg/env/active/bin:/opt/pmk/env/global/bin:/Users/USER/.local/bin"
QTERM_SESSION_ID = "3d15a54476bb450da6cbdda5a861850e"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "2.0.0"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.apple.Terminal"
```

まず Docker Desktop のデーモンが実行中かどうかを確認し、次に /tmp とローカルフォルダーへの書き込みを比較します。issue に記載されている Ava Reveal のパスと属性を、提供されている ls および xattr コマンドを使って確認し、利用可能であれば DLP ログを調べます。CLI と外部 DLP ポリシーのどちらに原因があるかを特定し、再現可能な証拠を文書化できれば完了です。

索引モデルが issue の本文から書いたものです。