davsclaus opened a new pull request, #27955: URL: https://github.com/apache/camel/pull/27955
Follow-up of [CAMEL-25388](https://issues.apache.org/jira/browse/CAMEL-25388) (the CLI for AI agents and scripts). Since Camel 4.21 the connector reads an action from a file of its own (`<pid>-action-<id>.json`, answered in `<pid>-output-<id>.json`), so that two clients asking the same integration at once cannot overwrite each other's action or answer. CAMEL-25391/25393 moved the `camel cmd` and `camel get` commands to it with `ActionClient`, and the monitor already uses it (`MonitorContext`, with the shared file as the fallback for an older integration). ### camel debug - `camel debug` was the last command that always wrote the shared `<pid>-action.json`: a step, step over or skip over, and the attach of `--remote-attach`. It now sends them with `ActionClient.send`: a file per command for Camel 4.21 or later, the shared file only for an older integration, and it waits until the integration took the command (5 seconds at most). - `--remote-attach` exits with the exit code of the attach when the integration does not take it (it went on as if attached). ### Deprecated - `CamelCommand.getActionFile` and `getOutputFile` are no longer used, and are deprecated for plugin commands in favour of `ActionClient` (kept, as plugins outside Camel may call them). ### Docs - 4.24 upgrade guide: "the shared action file is deprecated for plugin commands". ### Tests - `DebugCommandTest`: with a fake integration, a debug command of Camel 4.24 goes in a file of its own and its answer is removed; an integration of Camel 4.20 gets the shared file and takes the command without confirming it. - `mvn test` of camel-jbang-core: all tests pass; camel-jbang-plugin-tui compiles. _Claude Code on behalf of davsclaus_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01DDRLJAyf8cDXSg8iX785My -- 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]
