davsclaus opened a new pull request, #1826: URL: https://github.com/apache/camel-website/pull/1826
The fourth post in the local-model benchmark series, after [the first](https://camel.apache.org/blog/2026/09/camel-local-model-benchmark/), [round 2](https://camel.apache.org/blog/2026/09/camel-local-model-benchmark-round-2/) and [round 3](https://camel.apache.org/blog/2026/10/camel-local-model-benchmark-round-3/). It frames the series as making Camel easy to use for any AI model, especially models small enough to run on a laptop or a mini PC, and keeps to the highlights: - **On to intermediate examples.** Six new examples (Kafka, JMS request-reply on Artemis, enrich and dedupe, dynamic routing, code-first REST, an LLM in a route) went from 37 to 64 percent of the steps in three nights, with fixes merged each day. - **Bugs that people hit too.** The pollEnrich timeout bug (CAMEL-25860, also fixed for 4.22.3 and 4.18.6) and four more runtime bugs. - **The docs.** YAML examples on 64 more component pages and for every data format, and the EIP examples in Java, XML and YAML. - **A Camel CLI that any agent can rely on** (CAMEL-25388): exit codes, `--json`, no waiting for a terminal, `camel log --previous`, and the CLI's own fixes, docs and tests (more than 2,300 in the module with the CLI commands, three times as many as in 4.22). - **Also new.** Lenient input, false passes fixed in our own benchmark, and a newer model that scored lower. - **Next.** Knowing what the message body is at every step, in every component, EIP, data format and language (CAMEL-24961). That work gets its own post later. All numbers are from the runs of Oct 9 to 21 on Camel main; the fixes ship in Camel 4.24. The featured image is the one from the earlier rounds. 🤖 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]
