JiriOndrusek opened a new pull request, #8995:
URL: https://github.com/apache/camel-quarkus/pull/8995

   fixes https://github.com/apache/camel-quarkus/issues/8993
   relates to https://github.com/apache/camel-quarkus/issues/8992
   
   `CamelAiToolProvider` now ignores requests from Camel `langchain4j-agent` 
endpoints — Camel agents select registry tools via their endpoint's `tags` 
parameter, while `@RegisterAiService` and user-built `AiServices` keep 
receiving all registered tools (restrictable with `@CamelAiTools`). Previously 
the auto-discovered provider attached every `ai-tool:` route to every agent 
request: breaking agents on models without tool support, duplicating specs on 
tagged agents, and leaking tools into unrelated conversations. Documented in 
the `ai-tool` usage doc.
   
   Also repairs the `langchain4j-agent-ql4j` recordings after #8985 (3 stubs, 
word-level edits — review with `git diff --word-diff`) and makes the custom 
AiService model configurable so the module works against a real Ollama.
   
   Verified: `langchain4j-agent-ql4j` 16/16 (also 16/16 against real Ollama, 
was 3/16), `langchain4j-agent` 15/15, `ai-tool-langchain4j` 8/8, 
`rag-bridge-ql4j` 11/11.
   
   ---
   _This PR was prepared by Claude Code on behalf of Jiri Ondrusek._
   
   <!-- Uncomment and fill this section if your PR is not trivial
   [ ] An issue should be filed for the change unless this is a trivial change 
(fixing a typo or similar). One issue should ideally be fixed by not more than 
one commit and the other way round, each commit should fix just one issue, 
without pulling in other changes.
   [ ] Each commit in the pull request should have a meaningful and properly 
spelled subject line and body. Copying the title of the associated issue is 
typically enough. Please include the issue number in the commit message 
prefixed by #.
   [ ] The pull request description should explain what the pull request does, 
how, and why. If the info is available in the associated issue or some other 
external document, a link is enough.
   [ ] Phrases like Fix #<issueNumber> or Fixes #<issueNumber> will auto-close 
the named issue upon merging the pull request. Using them is typically a good 
idea.
   [ ] Please run mvn process-resources -Pformat (and amend the changes if 
necessary) before sending the pull request.
   [ ] Contributor guide is your good friend: 
https://camel.apache.org/camel-quarkus/latest/contributor-guide.html
   -->


-- 
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]

Reply via email to