davsclaus opened a new pull request, #27515: URL: https://github.com/apache/camel/pull/27515
Three fixes to the camel-jbang monitor's MCP server, one commit each. **CAMEL-25424: camel_control acts on the integration it names** - The monitor's `camel_control` ignored the `name` argument (name or pid) and always acted on the selected integration. An agent asking to stop app A while B was selected stopped B. - It now acts on the integration or infra service it names, which also becomes the selected one, so the screen shows what the agent acts on. - With no name, it acts on the selected integration, or on the only one running. - An unknown name gets an error that lists what is running. **CAMEL-25426: the Overview table is up to date for an agent on any tab** - On the other tabs the monitor refreshes only the selected integration. An agent reading the Overview table from there got stale rows for the others: an app started a minute earlier still read "0/1 ready, uptime 2s". - The read now asks for a scan of every integration and waits for it, at most 4 seconds. **CAMEL-25426: say which tabs the monitor lists to an agent** - The tool description said it lists every tab. It actually lists the tabs that apply to the selected integration, or all of them when none is selected. - SQL Query, for example, appears once the integration reports a data source. Verified live with the sql and timer-log examples: - stop-routes and start-routes by name worked while the other app was selected. - The Overview rows of the non-selected app kept advancing while the Log tab was active. Tests: new `McpFacadeControlTest` and `McpFacadeFullScanTest`. All 1766 tests in camel-jbang-plugin-tui pass. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m -- 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]
