:wave: another question - it looks like `koog-agen...
# koog-agentic-framework
r
πŸ‘‹ another question - it looks like
koog-agents
brings in a redis dependency. We found out after a lot of debugging that this brings in a specific version of netty - which breaks another library that we have in place for Pulsar and caused it to behave differently.
Copy code
ai.koog:koog-agents:0.7.2          (umbrella)
    └── ai.koog:prompt-cache-redis:0.7.2
          └── io.lettuce:lettuce-core:7.2.1.RELEASE
                └── io.netty:netty-resolver-dns:4.2.5.Final  ← breaks Pulsar
Is there a specific reason to include
prompt-cache-redis
in the core koog-agents? Wonder if that was by design or an oversight...
v
koog-agents is all-in-one dependency meant for quick start. It comes with nearly everything except jvm-only (Spring) or niche (file system tools) parts of Koog
You probably should consider using finer-grained dependencies, please check here: https://mvnrepository.com/artifact/ai.koog You can match them with the modules of Koog on GitHub (or you can ask Claude or Junie to do that for you based on your current used imports). Please let me know if you need any help with picking the right dependencies.
r
Yes, that's the approach we went with. Thanks
πŸ‘ 1