You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2026/10/10 06:31:00 UTC

[jira] [Resolved] (CAMEL-25513) camel-jbang-mcp - a write reports the reload and the first output of the integration running from its directory

     [ https://issues.apache.org/jira/browse/CAMEL-25513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-25513.
---------------------------------
    Resolution: Fixed

> camel-jbang-mcp - a write reports the reload and the first output of the integration running from its directory
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-25513
>                 URL: https://issues.apache.org/jira/browse/CAMEL-25513
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Priority: Major
>             Fix For: 4.23.0
>
>
> camel_write_file and camel_edit_file report what a dev-mode integration did with the written file (CAMEL-24859) only when the tool knows the integration: a selected process. Through camel-jbang-mcp an agent passes the project directory and no integration name, so no write reports a reload: in a run of the local-model benchmark ladder none of the 68 step traces got one, and the answer only says "An integration running the file in dev mode reloads it now". The agent writes blind: in the transform-xslt example the model's stylesheet produced <packingSlip orderId="" country=""/>, it read the log before the reload had run, and declared the step done.
> Proposal:
> * when no integration is selected, the write tools look up the dev-mode integration running from the directory (as camel_run does to avoid a second copy) and await its reload
> * after a reload, the answer carries the first lines the routes logged (and any WARN or ERROR) within a few seconds, so the agent sees the result of its change at once: "After the reload it logged: Packing slip: <packingSlip orderId=\"\" ..."



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