[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [agentic-ai-dev] Consensus on API
|
For me I think I am not missing anything, except adding tool calling support for LargeLanguageModel interface (
https://github.com/jakartaee/agentic-ai/blob/main/api/src/main/java/jakarta/ai/agent/LargeLanguageModel.java). This would be used in many agents for sure, and defining in the API would require that any LLM provider should make the impl.
This would need another Record for storing ToolResponse, and probably creating other ones (such as ToolCall, have to think a little bit...).
Other option is let as it is, without defining in this API explicitly, and implement using <T> T query(String prompt, Class<T> resultType); somehow, but the tool call should be implemented somewhere else.
Folks,
Our next step is to publish the API to Maven staging. This will effectively make it available to developers. Before we do that step, I would like to reach committer consensus.
I do hope that by now you have taken some time to review the context. I now ask that you carefully review the proposed API:
https://github.com/jakartaee/agentic-ai/tree/main/api. While the specification document will have a lot more details, a great deal of the behavior is actually already documented in the API Javadoc.
Please provide your feedback and comments here. I will spin out separate threads to keep the discussion focused if necessary. I would like to see if we can achieve consensus by Friday. In that spirit, if everything looks good from a v1 perspective, I ask that you please respond with a +1 so I can count your vote.
Onward!
Cheers,
Reza
agentic-ai-dev mailing list
agentic-ai-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
-- ----------------------------
Juan G.
