[jira] [Work started] (CAMEL-25441) camel-jbang-plugin-tui - confirm AI panel tool execution for parity with the ACP permission flow

["Claus Ibsen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CAMEL-25441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on CAMEL-25441 started by Claus Ibsen.
-------------------------------------------
> camel-jbang-plugin-tui - confirm AI panel tool execution for parity with the ACP permission flow
> ------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-25441
>                 URL: https://issues.apache.org/jira/browse/CAMEL-25441
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang
>            Reporter: Andrea Cosentino
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.24.0
>
>
> In the Camel TUI's built-in AI panel (direct LLM providers), the tools the model requests are executed immediately (AiPanel.runAgentLoop -> executeTuiTool -> TuiToolRegistry.execute). The ACP agent path, by contrast, routes every tool that is not in TuiToolRegistry.READ_ONLY_TOOLS through a user permission popup (AiPanel.AcpPanelPermissionHandler).
> For consistency, and to keep the user in control of the actions the assistant performs (writing files, controlling integrations, sending messages, etc.), the built-in panel should apply the same policy: prompt for confirmation on tools that are not read-only, reusing the existing READ_ONLY_TOOLS set and the permission popup. This makes the two AI entry points behave the same way.
> Module: dsl/camel-jbang/camel-jbang-plugin-tui (AiPanel).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)