[jira] [Created] (CAMEL-24861) camel-jbang-mcp - camel_run starts with --source-dir so files added later are part of the app, and camel_control gets a reload action

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

Claus Ibsen created CAMEL-24861:
-----------------------------------

             Summary: camel-jbang-mcp - camel_run starts with --source-dir so files added later are part of the app, and camel_control gets a reload action
                 Key: CAMEL-24861
                 URL: https://issues.apache.org/jira/browse/CAMEL-24861
             Project: Camel
          Issue Type: Improvement
          Components: camel-jbang
            Reporter: Claus Ibsen


Found by the stepwise half of the round-2 local-model benchmark (ten camel-jbang-examples built step by step through the camel-jbang-mcp server, five runs each, 2026-09-21).

Two gaps met while building an integration step by step through the MCP server:

* {{camel_run}} starts {{camel run <files> --dev}} with the route files of the moment. A file the agent adds afterwards (beans.yaml, a Java class, a second route file) is not part of the app, and {{camel_control restart}} replays the same command line, so a restart does not help either. {{camel run --source-dir=<dir> --dev}} watches the whole directory, new files included, which is what an agent building a project needs. The tool should start that way (an option to keep the explicit file list can stay for the case where a directory holds several apps).
* {{camel_control}} has stop, kill, restart, stop-routes, start-routes and reset-stats, but no reload, while the CLI has {{camel cmd reload}} (the action file the reload dev console reads). A reload re-runs the routes without a restart: a changed stylesheet or a dropped data file takes effect, and files consumed once are read again. Add {{reload}} to the actions.



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