This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch feature/CAMEL-23722-cli-docs-restructure
in repository https://gitbox.apache.org/repos/asf/camel.git

commit 8a4890adee8009a1838f32053098529621ded5f4
Author: Claus Ibsen <[email protected]>
AuthorDate: Tue Jun 9 20:39:20 2026 +0200

    CAMEL-23722: Mention TUI auto-install in tips
    
    Co-Authored-By: Claude Opus 4.6 <[email protected]>
    Signed-off-by: Claus Ibsen <[email protected]>
---
 docs/user-manual/modules/ROOT/pages/camel-jbang-debugging.adoc       | 3 ++-
 docs/user-manual/modules/ROOT/pages/camel-jbang-getting-started.adoc | 4 ++--
 docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc        | 5 +++--
 3 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-debugging.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-jbang-debugging.adoc
index 1dea78edf732..38da7147b32b 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-debugging.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-debugging.adoc
@@ -2,7 +2,8 @@
 
 The Camel CLI provides built-in debugging capabilities — from Camel's own 
route debugger to standard Java debugging. For the full overview, see 
xref:camel-jbang.adoc[Camel CLI].
 
-TIP: The xref:camel-jbang-tui.adoc[Camel TUI] includes a Spans tab that shows 
OpenTelemetry traces
+TIP: Just type `camel tui` — the plugin auto-installs on first use.
+The xref:camel-jbang-tui.adoc[Camel TUI] includes a Spans tab that shows 
OpenTelemetry traces
 as a waterfall view — useful for understanding message flow and spotting slow 
processors.
 
 == Camel route debugging
diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-jbang-getting-started.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-jbang-getting-started.adoc
index 166d11bed95b..7cb3d3e771c4 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-getting-started.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-getting-started.adoc
@@ -84,8 +84,8 @@ TIP: Dev mode is the fastest way to prototype integrations.
 Keep it running while you iterate on your routes.
 
 TIP: Want a visual overview of your running routes, message flow, and health 
status — right in the terminal?
-Try the xref:camel-jbang-tui.adoc[Camel TUI] (`camel tui`), a full-featured 
dashboard that works
-over SSH, in containers, and anywhere a browser is not available.
+Just type `camel tui` — the plugin auto-installs on first use, no setup needed.
+See xref:camel-jbang-tui.adoc[Camel TUI] for details.
 
 == Try a built-in example
 
diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc
index b972290eae41..0ad15e733c2e 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang-managing.adoc
@@ -3,8 +3,9 @@
 Once your Camel integrations are running, the CLI provides comprehensive 
management and monitoring capabilities — from listing processes and tailing 
logs to tracing messages and checking health.
 
 TIP: Prefer a visual dashboard over individual commands?
-The xref:camel-jbang-tui.adoc[Camel TUI] (`camel tui`) shows routes, messages, 
health, traces,
-and more in a single terminal view — everything on this page, at a glance.
+Just type `camel tui` — the plugin auto-installs on first use.
+It shows routes, messages, health, traces, and more in a single terminal view.
+See xref:camel-jbang-tui.adoc[Camel TUI] for details.
 
 == Controlling local Camel integrations
 

Reply via email to