This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 38ba8bef5b6c chore: camel-jbang - docs page comparing the ways to use
AI (#27653)
38ba8bef5b6c is described below
commit 38ba8bef5b6c8a27f804a78e81a004a651fa9c6d
Author: Claus Ibsen <[email protected]>
AuthorDate: Sat Oct 10 11:00:52 2026 +0200
chore: camel-jbang - docs page comparing the ways to use AI (#27653)
New page with a diagram that puts the AI panel with a provider, a coding
agent over ACP, an agent over the MCP server and camel mcp side by side,
linked from the related pages.
Signed-off-by: Claus Ibsen <[email protected]>
Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]>
---
.../ROOT/images/jbang/camel-tui-ai-ways.svg | 179 +++++++++++++++++++++
docs/user-manual/modules/ROOT/nav.adoc | 1 +
.../modules/ROOT/pages/camel-jbang-mcp.adoc | 3 +
.../ROOT/pages/camel-jbang-tui-ai-agents.adoc | 3 +
.../ROOT/pages/camel-jbang-tui-ai-ways.adoc | 138 ++++++++++++++++
.../modules/ROOT/pages/camel-jbang-tui-ai.adoc | 3 +
.../modules/ROOT/pages/camel-jbang-tui.adoc | 5 +-
7 files changed, 331 insertions(+), 1 deletion(-)
diff --git a/docs/user-manual/modules/ROOT/images/jbang/camel-tui-ai-ways.svg
b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-ai-ways.svg
new file mode 100644
index 000000000000..9b2c968cf7c7
--- /dev/null
+++ b/docs/user-manual/modules/ROOT/images/jbang/camel-tui-ai-ways.svg
@@ -0,0 +1,179 @@
+<svg xmlns="http://www.w3.org/2000/svg"; viewBox="0 0 1240 800" width="1240"
height="800" font-family="-apple-system, 'Segoe UI', Helvetica, Arial,
sans-serif" role="img" aria-labelledby="title desc">
+ <title id="title">Four ways to use AI with the Camel TUI</title>
+ <desc id="desc">Built-in AI panel, coding agent over ACP, external agent
over the TUI MCP server, and the standalone camel mcp server. The first three
reach Camel through the TUI tool registry, the fourth reaches running
integrations and the catalog without the TUI.</desc>
+ <defs>
+ <marker id="arrow" viewBox="0 0 10 10" refX="9" refY="5" markerWidth="7"
markerHeight="7" orient="auto-start-reverse">
+ <path d="M0,0 L10,5 L0,10 z" fill="#555"/>
+ </marker>
+ <style>
+ .bg { fill: #ffffff; }
+ .h1 { font-size: 22px; font-weight: 700; fill: #1f2328; }
+ .sub { font-size: 13px; fill: #57606a; }
+ .num { font-size: 22px; font-weight: 700; fill: #ffffff; }
+ .colt { font-size: 16px; font-weight: 700; fill: #ffffff; }
+ .cols { font-size: 12px; fill: #ffffff; }
+ .lbl { font-size: 10px; font-weight: 700; letter-spacing: 0.08em; fill:
#6e7781; }
+ .t { font-size: 13px; fill: #1f2328; }
+ .tb { font-size: 13px; font-weight: 700; fill: #1f2328; }
+ .edge { font-size: 11px; fill: #444c56; font-style: italic; }
+ .code { font-family: 'SFMono-Regular', Menlo, Consolas, monospace;
font-size: 12px; fill: #1f2328; }
+ .line { stroke: #555; stroke-width: 1.6; fill: none; }
+ .box { stroke-width: 1.5; }
+ </style>
+ </defs>
+
+ <rect class="bg" x="0" y="0" width="1240" height="800"/>
+
+ <text class="h1" x="30" y="40">Four ways to use AI with the Camel TUI</text>
+ <text class="sub" x="30" y="62">Where you type, who runs the model, and how
the Camel tools are reached</text>
+
+ <!-- ===================== Column 1: built-in AI ===================== -->
+ <g>
+ <rect x="30" y="85" width="280" height="62" rx="8" fill="#2f6fdf"/>
+ <text class="num" x="46" y="124">1</text>
+ <text class="colt" x="72" y="111">Built-in AI panel</text>
+ <text class="cols" x="72" y="131">F8 with an LLM provider</text>
+
+ <rect class="box" x="30" y="170" width="280" height="64" rx="8"
fill="#eaf1fd" stroke="#2f6fdf"/>
+ <text class="lbl" x="44" y="189">YOU TYPE IN</text>
+ <text class="tb" x="44" y="210">The TUI AI panel (F8)</text>
+ <text class="t" x="44" y="226">or Shift+F8 "fix with AI"</text>
+
+ <rect class="box" x="30" y="282" width="280" height="80" rx="8"
fill="#eaf1fd" stroke="#2f6fdf"/>
+ <text class="lbl" x="44" y="301">THE MODEL</text>
+ <text class="tb" x="44" y="322">LLM provider, called by the TUI</text>
+ <text class="t" x="44" y="339">Anthropic, OpenAI, Gemini, or local:</text>
+ <text class="t" x="44" y="355">Ollama, LM Studio, vLLM ...</text>
+
+ <rect class="box" x="30" y="410" width="280" height="64" rx="8"
fill="#eaf1fd" stroke="#2f6fdf"/>
+ <text class="lbl" x="44" y="429">CAMEL TOOLS VIA</text>
+ <text class="tb" x="44" y="450">In-process, no MCP</text>
+ <text class="t" x="44" y="466">the panel runs the tool calls itself</text>
+
+ <path class="line" d="M170,234 L170,280" marker-end="url(#arrow)"/>
+ <text class="edge" x="178" y="262">HTTP API</text>
+ <path class="line" d="M170,362 L170,408" marker-end="url(#arrow)"/>
+ <text class="edge" x="178" y="390">tool calls</text>
+ <path class="line" d="M170,474 L170,518" marker-end="url(#arrow)"/>
+ </g>
+
+ <!-- ===================== Column 2: ACP agent ===================== -->
+ <g>
+ <rect x="330" y="85" width="280" height="62" rx="8" fill="#8a4fd6"/>
+ <text class="num" x="346" y="124">2</text>
+ <text class="colt" x="372" y="111">Coding agent in the panel</text>
+ <text class="cols" x="372" y="131">F8, Ctrl+P, pick an acp: provider</text>
+
+ <rect class="box" x="330" y="170" width="280" height="64" rx="8"
fill="#f3ecfc" stroke="#8a4fd6"/>
+ <text class="lbl" x="344" y="189">YOU TYPE IN</text>
+ <text class="tb" x="344" y="210">The TUI AI panel (F8)</text>
+ <text class="t" x="344" y="226">the agent's answers show there</text>
+
+ <rect class="box" x="330" y="282" width="280" height="80" rx="8"
fill="#f3ecfc" stroke="#8a4fd6"/>
+ <text class="lbl" x="344" y="301">THE MODEL</text>
+ <text class="tb" x="344" y="322">ACP agent started by the TUI</text>
+ <text class="t" x="344" y="339">Claude Code, Codex, opencode, Qwen
...</text>
+ <text class="t" x="344" y="355">with its own model and login</text>
+
+ <rect class="box" x="330" y="410" width="280" height="64" rx="8"
fill="#f3ecfc" stroke="#8a4fd6"/>
+ <text class="lbl" x="344" y="429">CAMEL TOOLS VIA</text>
+ <text class="tb" x="344" y="450">TUI MCP server, started for it</text>
+ <text class="t" x="344" y="466">random port on 127.0.0.1</text>
+
+ <path class="line" d="M470,234 L470,280" marker-end="url(#arrow)"/>
+ <text class="edge" x="478" y="262">ACP over stdio</text>
+ <path class="line" d="M470,362 L470,408" marker-end="url(#arrow)"/>
+ <text class="edge" x="478" y="390">MCP over HTTP</text>
+ <path class="line" d="M470,474 L470,518" marker-end="url(#arrow)"/>
+ </g>
+
+ <!-- ===================== Column 3: external agent over the TUI MCP server
===================== -->
+ <g>
+ <rect x="630" y="85" width="280" height="62" rx="8" fill="#0f8f7a"/>
+ <text class="num" x="646" y="124">3</text>
+ <text class="colt" x="672" y="111">Your agent drives the TUI</text>
+ <text class="cols" x="672" y="131">camel tui --mcp</text>
+
+ <rect class="box" x="630" y="170" width="280" height="64" rx="8"
fill="#e6f5f2" stroke="#0f8f7a"/>
+ <text class="lbl" x="644" y="189">YOU TYPE IN</text>
+ <text class="tb" x="644" y="210">Your agent, in its own window</text>
+ <text class="t" x="644" y="226">the TUI is the screen you share</text>
+
+ <rect class="box" x="630" y="282" width="280" height="80" rx="8"
fill="#e6f5f2" stroke="#0f8f7a"/>
+ <text class="lbl" x="644" y="301">THE MODEL</text>
+ <text class="tb" x="644" y="322">Your agent's own model</text>
+ <text class="t" x="644" y="339">Claude Code, Codex, Cursor, any</text>
+ <text class="t" x="644" y="355">MCP client</text>
+
+ <rect class="box" x="630" y="410" width="280" height="64" rx="8"
fill="#e6f5f2" stroke="#0f8f7a"/>
+ <text class="lbl" x="644" y="429">CAMEL TOOLS VIA</text>
+ <text class="tb" x="644" y="450">TUI MCP server</text>
+ <text class="t" x="644" y="466">localhost:8123 (--mcp-port)</text>
+
+ <path class="line" d="M770,234 L770,280" marker-end="url(#arrow)"/>
+ <text class="edge" x="778" y="262">your terminal / IDE</text>
+ <path class="line" d="M770,362 L770,408" marker-end="url(#arrow)"/>
+ <text class="edge" x="778" y="390">MCP over HTTP</text>
+ <path class="line" d="M770,474 L770,518" marker-end="url(#arrow)"/>
+ </g>
+
+ <!-- ===================== Column 4: camel mcp, no TUI =====================
-->
+ <g>
+ <rect x="930" y="85" width="280" height="62" rx="8" fill="#c26a12"/>
+ <text class="num" x="946" y="124">4</text>
+ <text class="colt" x="972" y="111">Camel MCP server, no TUI</text>
+ <text class="cols" x="972" y="131">camel mcp</text>
+
+ <rect class="box" x="930" y="170" width="280" height="64" rx="8"
fill="#fcf0e3" stroke="#c26a12"/>
+ <text class="lbl" x="944" y="189">YOU TYPE IN</text>
+ <text class="tb" x="944" y="210">Your agent, in its own window</text>
+ <text class="t" x="944" y="226">no TUI needed</text>
+
+ <rect class="box" x="930" y="282" width="280" height="80" rx="8"
fill="#fcf0e3" stroke="#c26a12"/>
+ <text class="lbl" x="944" y="301">THE MODEL</text>
+ <text class="tb" x="944" y="322">Your agent's own model</text>
+ <text class="t" x="944" y="339">Claude Code, Codex, Cursor, any</text>
+ <text class="t" x="944" y="355">MCP client</text>
+
+ <rect class="box" x="930" y="410" width="280" height="64" rx="8"
fill="#fcf0e3" stroke="#c26a12"/>
+ <text class="lbl" x="944" y="429">CAMEL TOOLS VIA</text>
+ <text class="tb" x="944" y="450">camel mcp server</text>
+ <text class="t" x="944" y="466">stdio (or HTTP), started by the
agent</text>
+
+ <path class="line" d="M1070,234 L1070,280" marker-end="url(#arrow)"/>
+ <text class="edge" x="1078" y="262">your terminal / IDE</text>
+ <path class="line" d="M1070,362 L1070,408" marker-end="url(#arrow)"/>
+ <text class="edge" x="1078" y="390">MCP over stdio</text>
+ <path class="line" d="M1070,474 L1070,618" marker-end="url(#arrow)"/>
+ <text class="edge" x="1078" y="550">catalog + camel_* tools,</text>
+ <text class="edge" x="1078" y="565">no tui_* tools</text>
+ </g>
+
+ <!-- ===================== Shared TUI band (columns 1-3)
===================== -->
+ <rect class="box" x="30" y="520" width="880" height="76" rx="8"
fill="#f6f8fa" stroke="#57606a"/>
+ <text class="tb" x="46" y="545">Camel TUI tool registry: the same tools
whichever way you came in</text>
+ <text class="t" x="46" y="565">tui_* tools see and drive the screen: tabs,
tables, traces, errors, logs, diagrams, drawing</text>
+ <text class="t" x="46" y="583">camel_* tools build and run: catalog docs,
validate, read and write sources (writes wait for your OK)</text>
+ <path class="line" d="M470,596 L470,618" marker-end="url(#arrow)"/>
+
+ <!-- ===================== Bottom band (all) ===================== -->
+ <rect class="box" x="30" y="620" width="1180" height="60" rx="8"
fill="#ffffff" stroke="#1f2328"/>
+ <text class="tb" x="46" y="645">Your Camel integrations and project</text>
+ <text class="t" x="46" y="665">running integrations (camel run, Spring Boot,
Quarkus) through ~/.camel, route source files, the Camel catalog</text>
+
+ <!-- ===================== How to start ===================== -->
+ <text class="lbl" x="30" y="712">HOW TO START</text>
+ <text class="code" x="30" y="734">camel tui</text>
+ <text class="t" x="30" y="754">then F8 (provider from env or Ctrl+P)</text>
+
+ <text class="code" x="330" y="734">camel tui</text>
+ <text class="t" x="330" y="754">then F8, Ctrl+P, acp:claude, acp:codex
...</text>
+
+ <text class="code" x="630" y="734">camel tui --mcp</text>
+ <text class="t" x="630" y="754">and add http://localhost:8123/mcp</text>
+ <text class="t" x="630" y="772">to your agent's MCP config</text>
+
+ <text class="code" x="930" y="734">camel mcp</text>
+ <text class="t" x="930" y="754">registered as an MCP server in your</text>
+ <text class="t" x="930" y="772">agent's config</text>
+</svg>
diff --git a/docs/user-manual/modules/ROOT/nav.adoc
b/docs/user-manual/modules/ROOT/nav.adoc
index 376c02502415..adf612736113 100644
--- a/docs/user-manual/modules/ROOT/nav.adoc
+++ b/docs/user-manual/modules/ROOT/nav.adoc
@@ -30,6 +30,7 @@
**** xref:camel-jbang-tui-source-editor.adoc[Camel TUI Source Editor]
**** xref:camel-jbang-tui-diagram.adoc[Camel TUI Diagram]
**** xref:camel-jbang-tui-observe.adoc[Camel TUI Observing Integrations]
+**** xref:camel-jbang-tui-ai-ways.adoc[Camel TUI Ways to Use AI]
**** xref:camel-jbang-tui-ai.adoc[Camel TUI AI Panel]
**** xref:camel-jbang-tui-local-models.adoc[Camel TUI Local Models]
**** xref:camel-jbang-tui-ai-agents.adoc[Camel TUI and AI Agents]
diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-mcp.adoc
b/docs/user-manual/modules/ROOT/pages/camel-jbang-mcp.adoc
index e39157d531ff..6b6293195090 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-mcp.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-mcp.adoc
@@ -13,6 +13,9 @@ Camel applications — without you having to copy-paste
anything.
Built on https://quarkus.io/[Quarkus] with the
https://docs.quarkiverse.io/quarkus-mcp-server/dev/index.html[quarkus-mcp-server]
extension.
+The Camel TUI has an MCP server of its own, `camel tui --mcp`, that also lets
an agent see and drive the TUI screen;
+see xref:camel-jbang-tui-ai-ways.adoc[Camel TUI Ways to Use AI] for how the
two compare.
+
== Getting Started
The quickest way to get started:
diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-ai-agents.adoc
b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-ai-agents.adoc
index 3ba4c8e8cba2..149511bec45c 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-ai-agents.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-ai-agents.adoc
@@ -6,6 +6,9 @@ your confirmation.
See xref:camel-jbang-tui.adoc[Camel TUI] for getting started and the other
pages.
+TIP: Not sure whether you want the AI panel, a coding agent or an MCP server?
See
+xref:camel-jbang-tui-ai-ways.adoc[Camel TUI Ways to Use AI] for the options
side by side.
+
== Key Features
* <<_why_this_matters,*Same view as you*>> -- routes, statistics, traces,
errors, logs and sources
diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-ai-ways.adoc
b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-ai-ways.adoc
new file mode 100644
index 000000000000..7e001fb87753
--- /dev/null
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-ai-ways.adoc
@@ -0,0 +1,138 @@
+= Camel TUI Ways to Use AI
+
+There are several ways to bring AI into the Camel TUI, and they differ in
three things: where you type, who runs
+the model, and how the model reaches Camel. This page puts them side by side
so you can pick one; the pages linked
+from each section have the details.
+
+See xref:camel-jbang-tui.adoc[Camel TUI] for getting started and the other
pages.
+
+image::jbang/camel-tui-ai-ways.svg[Four ways to use AI with the Camel TUI: the
built-in AI panel, a coding agent in the panel over ACP, your own agent driving
the TUI over MCP, and the camel mcp server without the TUI]
+
+== At a glance
+
+[cols="1,2,2,2,2",options="header"]
+|===
+| | You type in | The model | Camel tools via | Start with
+
+| *1. Built-in AI panel*
+| The AI panel (*F8*) in the TUI
+| An LLM provider the TUI calls: Anthropic, OpenAI, Gemini, or a local model
through Ollama or an OpenAI-compatible server
+| The panel itself, in-process (no MCP)
+| `camel tui`, then *F8*
+
+| *2. Coding agent in the panel*
+| The AI panel (*F8*) in the TUI
+| An agent the TUI starts over ACP (Claude Code, Codex, opencode, Qwen, ...),
with its own model and login
+| The TUI's MCP server, started for the agent on a random localhost port
+| `camel tui`, then *F8*, *Ctrl+P* and an `acp:` provider
+
+| *3. Your agent drives the TUI*
+| Your agent, in its own terminal or IDE
+| Your agent's own model
+| The TUI's MCP server on `localhost:8123`
+| `camel tui --mcp`, and the server added to the agent's MCP configuration
+
+| *4. Camel MCP server, no TUI*
+| Your agent, in its own terminal or IDE
+| Your agent's own model
+| The `camel mcp` server, which the agent starts
+| `camel mcp`, registered in the agent's MCP configuration
+|===
+
+In the first three the model gets the same tools from the same place: the
TUI's tool registry. The `tui_*` tools
+see and drive the screen (tabs, tables, traces, errors, logs, diagrams,
drawing on the screen), and the `camel_*`
+tools build and run integrations (catalog documentation, validation, reading
and writing the route sources). The
+`camel_*` tools are the same ones the `camel mcp` server offers, so an agent
gets the same Camel through either door;
+only the `tui_*` tools need the TUI.
+
+== 1. The built-in AI panel
+
+Press *F8* and ask. The TUI is the agent: it sends your question to the model,
runs the tools the model asks for
+itself, and shows the answer. No MCP server is involved, and nothing runs
outside the TUI except the model.
+
+The provider is detected from the environment (`ANTHROPIC_API_KEY`,
`OPENAI_API_KEY`, `GEMINI_API_KEY`, a local
+Ollama, ...) and *Ctrl+P* switches it. With a local model nothing leaves your
machine, and the panel sends a smaller
+tool set to keep prompts short.
+
+Pick this when you want answers inside the TUI with no other tool installed,
or when you want to run a local model.
+
+* xref:camel-jbang-tui-ai.adoc[Camel TUI AI Panel] -- providers, slash
commands, AI project overview, AI log
+* xref:camel-jbang-tui-local-models.adoc[Camel TUI Local Models] -- Ollama,
OpenAI-compatible servers, what a question costs
+
+== 2. A coding agent in the panel (ACP)
+
+The same panel can hand the conversation to a coding agent instead of a model.
Press *Ctrl+P* in the panel and pick
+an `acp:` provider (`acp:claude`, `acp:codex`, `acp:opencode`, ...). The TUI
starts the agent as a subprocess and talks
+to it over the https://agentclientprotocol.com[Agent Client Protocol] (ACP).
The agent brings its own model, login,
+settings and skills; the TUI shows its answers, tool calls and permission
questions in the panel.
+
+To reach Camel the agent needs the TUI's tools, so the TUI starts its MCP
server for it on a random port on
+`127.0.0.1` and hands the address to the agent. You do not need `--mcp` for
this.
+
+Pick this when you already use a coding agent and want it inside the TUI, with
your subscription and its own tools
+(it can also edit files and run commands, each asked for in a popup).
+
+* xref:camel-jbang-tui-ai-agents.adoc#_using_a_coding_agent_acp[Using a coding
agent (ACP)]
+
+== 3. Your agent drives the TUI (MCP)
+
+Here you work in your agent (Claude Code in another terminal, an IDE
assistant, any MCP client) and the TUI is the
+screen you both look at. Start the TUI with `camel tui --mcp` and point the
agent at `http://localhost:8123/mcp`. The
+agent sees what you see and can act on it: switch tabs, select routes, send
test messages, start and stop routes,
+draw on the screen to show you something, and edit the route sources.
+
+Pick this when the agent is where you do your work and you want it to see and
steer the running integrations.
+
+* xref:camel-jbang-tui-ai-agents.adoc#_enabling_mcp[Enabling MCP] and
xref:camel-jbang-tui-ai-agents.adoc#_connecting_an_ai_agent[Connecting an AI
Agent]
+
+=== One MCP server, two ways to start it
+
+Ways 2 and 3 use the same MCP server inside the TUI, with the same tools. The
difference is only who starts it and
+who connects:
+
+[cols="1,2,2",options="header"]
+|===
+| | Way 2 (ACP) | Way 3 (`--mcp`)
+| Started | automatically, when an ACP agent needs it | by `camel tui --mcp`
+| Port | random | `8123`, or `--mcp-port`
+| Connected by | the agent the TUI started | any MCP client you configure
+|===
+
+Either way the server listens on `127.0.0.1` only, has no authentication, and
rejects requests from web pages.
+*F2* -> _AI & MCP_ -> _MCP Info_ shows the port and the client, and _MCP Log_
the calls it made.
+
+== 4. The Camel MCP server, without the TUI
+
+`camel mcp` is a separate MCP server that does not need the TUI at all. It
gives an agent the Camel catalog
+(components, EIPs, data formats, Kamelets, examples), the shared `camel_*`
authoring tools, and tools to inspect
+integrations started with `camel run`. It has no screen, so it has no `tui_*`
tools.
+
+Pick this when you do not use the TUI, or when the agent should know Camel
while you work elsewhere. It can run next
+to the TUI; the agent then has both servers.
+
+* xref:camel-jbang-mcp.adoc[Camel MCP Server]
+
+== What is the same in every way inside the TUI
+
+* *Changes to files wait for you.* A file the model writes through
`camel_write_file` is validated first, and then
+ shows a confirm dialog with the diff (or, with `/write live`, is typed into
the Source editor while you watch).
+ This holds for the built-in panel, an ACP agent and an external MCP agent
alike.
+* *You can see what happened.* The AI log (*F2* -> _AI & MCP_ -> _AI Log_)
records the questions, tool calls and
+ answers of the panel; the MCP log records the calls agents made through the
MCP server.
+* *The same shortcuts open the panel.* *Shift+F8* in the Source editor, the
Log tab and the Errors view writes the
+ question for you ("fix with AI") and sends it to whichever provider or agent
the panel uses. `/overview`, which
+ explains the project, needs a model (way 1); an agent explains it with the
`camel_project_overview` and
+ `camel_save_project_summary` tools when you ask it to.
+
+== Not the TUI's AI: LLM calls from your integration
+
+An integration can call an LLM itself, for example with the `openai` or
`langchain4j` components. That has nothing
+to do with the ways above, but the TUI shows it: with observability enabled on
the integration, *Ctrl+U* in the AI
+panel lists those calls as *integration* next to the panel's own (*TUI ask*).
+
+== Which one should I pick?
+
+* New to the TUI, or want to try a local model: *1*.
+* Already pay for a coding agent such as Claude Code or Codex and want it in
the TUI: *2*.
+* Already work in an agent and want it to see and drive your running
integrations: *3*.
+* No TUI, just Camel knowledge for your agent: *4*.
diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-ai.adoc
b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-ai.adoc
index 4dbfcf0f7314..b4b7d1d2051e 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-ai.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui-ai.adoc
@@ -6,6 +6,9 @@ models through Ollama, so nothing has to leave your machine
(see xref:camel-jban
See xref:camel-jbang-tui.adoc[Camel TUI] for getting started and the other
pages.
+TIP: Not sure whether you want the AI panel, a coding agent or an MCP server?
See
+xref:camel-jbang-tui-ai-ways.adoc[Camel TUI Ways to Use AI] for the options
side by side.
+
== Key Features
* <<_choosing_an_ai_provider,*Any provider*>> -- a hosted model or a local one
through Ollama or an OpenAI-compatible server
diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui.adoc
b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui.adoc
index 708e305cc35d..a5ee7fda7e58 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-tui.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-tui.adoc
@@ -95,7 +95,8 @@ and Routes shows the route count.
Two panels can be opened on top of any tab: *F6* opens an
xref:camel-jbang-tui-settings.adoc#_embedded_shell_f6[embedded shell]
for running `camel` commands, and *F8* opens the
xref:camel-jbang-tui-ai.adoc[AI panel] for asking
-questions about the running integrations.
+questions about the running integrations. The panel is one of several ways to
use AI with the TUI; see
+xref:camel-jbang-tui-ai-ways.adoc[Ways to Use AI] for how they compare.
== More about the TUI
@@ -110,6 +111,8 @@ fix with AI, completion, quick documentation, navigation,
live run data
| xref:camel-jbang-tui-diagram.adoc[Diagram] | The architecture, topology and
route views, external endpoints, metrics
| xref:camel-jbang-tui-observe.adoc[Observing Integrations] | Activity,
message history, errors, spans, process, HTTP
probe, CVE audit, Kafka, SQL, memory leaks, JFR, catalog
+| xref:camel-jbang-tui-ai-ways.adoc[Ways to Use AI] | The AI panel, a coding
agent over ACP, your agent over MCP, and
+`camel mcp`, side by side with a diagram
| xref:camel-jbang-tui-ai.adoc[AI Panel] | AI providers, slash commands,
project overview, AI log
| xref:camel-jbang-tui-local-models.adoc[Local Models] | Ollama and
OpenAI-compatible servers, the tool set for local
models, what a question costs, the Ollama tab
