toolsSettings.write.allowedPaths only auto-approves create, not strReplace or insert

[ABiegalski]

Description

When toolsSettings.write.allowedPaths is configured to auto-approve writes within a specific directory, only the create command is auto-approved. The strReplace and insert commands still prompt for user approval, even when the target file is within the allowed path.

Steps to Reproduce

1. Configure an agent with write path restrictions:

{
  "toolsSettings": {
    "write": {
      "allowedPaths": ["C:/example/workbench/**"]
    }
  }
}

2. Ensure write is not in the allowedTools array (to avoid blanket override).
3. Ask the agent to create a new file in the allowed path → auto-approves ✅
4. Ask the agent to strReplace content in that same file → prompts for approval ❌
5. Ask the agent to insert content into that same file → prompts for approval ❌

Expected Behavior

All three write commands (create, strReplace, insert) should be auto-approved when the target path matches allowedPaths.

Actual Behavior

Only create is auto-approved. strReplace and insert prompt the user for approval despite the file being within the allowed path.

Environment

• Kiro CLI on Windows 11
• Agent config uses toolsSettings.write.allowedPaths with glob pattern

[github-actions]

🤖 Potential Duplicate Detected

This issue appears to be similar to:

• #5071: Feature Request: Subagent tool approval improvements (85% similar)

What happens next?

• ⏰ This issue will be automatically closed in 3 days
• 🏷️ If this is not a duplicate, you can prevent automatic closure by adding a comment or reacting with 👎 to this message.
• 💬 Comment on the original issue if you have additional information

Why is this marked as duplicate?
Both issues report problems with tool approval settings not working as expected - the new issue describes allowedPaths not auto-approving strReplace/insert commands, while #5071 describes autoApproveTools not working for subagents. Both involve tool approval mechanisms failing to function properly despite being configured.

[ABiegalski]

This is not a duplicate of #5071. That issue is about autoApproveTools not working for subagents. This issue is about toolsSettings.write.allowedPaths not applying to strReplace and insert commands in the main agent — only create is auto-approved despite the file being within the allowed glob pattern. Different mechanism, different bug.

[github-actions]

Thank you for your feedback! 🙏

The duplicate label has been removed and this issue has been sent back for maintainer review.

A maintainer will review this issue shortly.

[AnilMaktala]

Hey @ABiegalski, Thanks for raising this. Could you please confirm the Kiro CLI version you are using? and are you using TUI or classic mode?

[ABiegalski]

Thanks for looking into this!

• Mode: TUI
• Kiro CLI Version: 2.2.0

The behavior is consistent — create commands to files within allowedPaths are auto-approved, but strReplace and insert to the same paths still prompt for approval. Happy to provide any additional config or logs if helpful.