davsclaus opened a new pull request, #27653: URL: https://github.com/apache/camel/pull/27653
## Summary There are several ways to use AI with the Camel CLI, and new users find it hard to tell them apart: the F8 AI panel with a provider, a coding agent in that panel over ACP, an agent connected to `camel tui --mcp`, and the standalone `camel mcp` server. This adds one page, **Camel TUI Ways to Use AI** (`camel-jbang-tui-ai-ways.adoc`), that puts them side by side: - a diagram (`images/jbang/camel-tui-ai-ways.svg`) with one column per way: where you type, who runs the model, and how the Camel tools are reached (in-process, the TUI MCP server, or `camel mcp`) - an at-a-glance table and a short section per way, linking to the existing detail pages - "one MCP server, two ways to start it": ACP starts it automatically on a random port, `--mcp` on 8123 - what is the same everywhere (confirmed file writes, AI and MCP logs, Shift+F8), and that `/overview` needs a model provider rather than an ACP agent - LLM calls made by the integration itself, which are not the CLI's AI but show up in Ctrl+U - which one to pick The page is added to the nav and linked from the TUI overview, AI panel, AI agents and Camel MCP Server pages. Docs only. The diagram is a plain SVG, because the website build has no Mermaid rendering. _Claude Code on behalf of davsclaus_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
