Skip to content

Granular tool trust picker not available in TUI v2 mode #6774

@BSwansonAW

Description

@BSwansonAW

Before opening, please confirm:

Operating System

Linux (WSL2 on Windows)

Kiro Version

Latest (chat.ui set to "tui")

Bug Description

When using TUI v2 (chat.ui "tui"), the granular trust picker introduced in v1.27 does not appear when prompted to approve tool usage. Instead, the TUI shows only basic Yes/Trust/No options without the tiered scope selection (e.g., Full command → Partial command → Base command → Entire Tool for shell, or Specific paths → Complete directory → Entire Tool for read/write).

The chat.disableGranularTrust setting is confirmed set to false in ~/.kiro/settings/cli.json.

The granular trust picker works correctly in the classic/legacy UI (kiro-cli chat --legacy-ui).

Steps to Reproduce

  1. kiro-cli settings chat.ui "tui"

  2. kiro-cli settings chat.disableGranularTrust false

  3. kiro-cli chat

  4. Ask the agent to perform an action requiring tool approval (e.g., a shell command or file write outside cwd)

  5. Observe that the approval prompt shows only Yes/Trust/No — no granular scope picker appears

  6. Compare with: kiro-cli chat --legacy-ui

  7. Same action now shows the full granular trust picker with tiered scope options

Expected Behavior

The TUI v2 approval UX should present the same granular trust picker as the legacy UI, allowing users to scope trust to exact commands, partial commands, base commands, specific paths, or directories — as documented in the v1.27 changelog and the TUI v2 docs which state: "For shell commands, you can trust at different granularity levels: exact commands, command prefixes, or base commands."

Additional Context

The TUI v2 documentation under "Approval UX" describes a "panel-based dropdown" with Yes/Trust/No and mentions granular shell command trust levels. However, in practice the tiered scope selection does not render. This may be a case where the disableGranularTrust setting is not wired into the TUI v2 code path, or the panel-based dropdown implementation doesn't include the picker component.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions