davsclaus opened a new pull request, #26627: URL: https://github.com/apache/camel/pull/26627
## Description The runtime side of CAMEL-24844 on a live app: what the body is at every step, answered where people and agents look. **The message dump** (`MessageHelper.dumpAsJSon`, what every backlog tracer event carries, so the message-history console, `camel trace` and the history file the CLI writes all get it): - `"type": "null"` when the body is null; it said nothing before, which read like "not captured"; - a `size` for text and byte bodies from the `MessageSizeStrategy` when it is enabled (the dev profile does): lengths only, nothing read or converted. Collections, arrays, files and stream caches already had one. **The camel-jbang history and error panels** parse the size and show it next to the type of each step's body, `Body: (String, 11 B)`. **The camel-jbang-mcp history tool** (`get_history`) gets `summary=true`: one entry per step with route, node, elapsed, and the body's type and size as it reached the step, without the bodies, headers and properties. The full dump of a last exchange costs thousands of tokens; the summary is what a small model reads to see where the body turned from text into a Map or bytes. Independent of #26626 (the message history entries and the failure table); together they give the type and size per step on every message (the history) and on the last completed one with its payloads (the tracer). ## Tests - camel-core `MessageHelperTest`: the size in the dump with the strategy enabled, and `"null"` for a null body. - camel-jbang-core `ToolRegistryTest`: the summary keeps route, node, elapsed, body type and size and drops the message. - camel-jbang-plugin-tui `StatusParserTest`: the size parsed from the dump, -1 without one; the prompt budget test still passes with the longer tool description. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj -- 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]
