Jose
10/27/2025, 10:20 AMAnastasiia Zarechneva
10/27/2025, 10:34 AMJCollardBovy
10/27/2025, 11:32 AMVadim Briliantov
10/27/2025, 12:10 PM@Deprecated annotation with replacement (where relevant) and still keep the existing API supported and working — feel free to search for Deprecations, Breaking Changes and Removals here: https://github.com/JetBrains/koog/releases
Before 1.0.0 we still would like to:
• polish and refine PromptExecutor/LLMClient/LLMProvider API
• provide Java API
• polish the nodes API and node naming (ex: nodeLLMRequest -> llmRequestNode change, and similar. Of course with deprecation and also keeping the older version working)
• provide integration with Spring AI
• Add integration with Quarkus, Micronaut
• Add integrations with major vector databases
(other integrations are also planned, as well as additions to the API, including new strategy types — but those are not a pre-requisite for a 1.0.0 release)
As for the date, we’re considering to have 1.0.0 around March/April approximately. This should provide us with enough time to finalize and polish everything.
But again — it doesn’t mean that Koog is not production ready (it is). And it doesn’t mean that we will be breaking the API all the time without providing deprecations and replacements (we always do).Jose
10/27/2025, 12:20 PMrcd27
10/27/2025, 2:17 PMlangchain implementation of deep-research-agent into Koog for couple of weeks, and this is just a mess of side-effects. Would agree to all Vadim's points.