<@UTC9JTKS8> - is there any progress on this?
# koog-agentic-framework
r
@Vadim Briliantov - is there any progress on this?
v
cc @Jakub Amanowicz 🙂
j
Hey @Ruben Cagnie, yes we have some progress 🙂 We have recently started releasing XCF binary of Koog. Soon, we will also start regular publications of
Package.swift
referring to this artifact. I expect this to be "officially usable" (meaning: we will have all workflows and additional repository configured and discoverable from xcode) in one of incoming releases. Until then, feel free to test it out - feedback is more than welcome! See our release for 0.6.4 - one of the assets is XCF binary:
Koog-0.6.4.xcframework.zip
The corresponding
Package.swift
would look as follows:
Copy code
// swift-tools-version:5.9
import PackageDescription

let package = Package(
    name: "Koog",
    platforms: [
        .iOS(.v13),
    ],
    products: [
        .library(
            name: "Koog",
            targets: ["Koog"]
        ),
    ],
    targets: [
        .binaryTarget(
            name: "Koog",
            url: "https://github.com/JetBrains/koog/releases/download/0.6.4/Koog-0.6.4.xcframework.zip",
            checksum: "7c30c0fcf9150691fdd957d1156cd33a58c6b886e50de9cdfccae58c3b8e57c6"
        ),
    ]
)
One caveat to have in mind is that modularity is impossible with K/N ObjectiveC export - we currently ship Koog as 1 large binary. We are aware of experimental Swift export feature for multiple modules but we haven't incorporated that yet (tbh it'd only help with namespaces and you would still have to download the whole binary)
r
That's really nice. But pulling in 34MB for just 1 client feels a bit large 😞
👍 1
Any thoughts on creating a xcframework per module?
m
[...] pulling in 34MB for just 1 client feels a bit large
Android has this issue as well, even after ProGuard. Koog adds ~20 MB to the final artifact. In one project we used Koog for prototyping, then cherry-picked only the pieces we needed once it worked. That may be harder on iOS. In the end, the agentic harness is just a while loop, so if binary size matters I'd probably write my own 🤷
v
For Android you can include individual fine-grained packages instead of the
koog-agents
all-in-one dependency. Please feel free to check them out here: https://mvnrepository.com/artifact/ai.koog • agents-core • agents-tools • prompt-model • etc.
💡 1
🚀 1
For iOS I believe @Jakub Amanowicz will later on split into individual XCF packages, too.
yes black 1
r
That would be great. We are specifically interested in the a2a client
j
Hey folks! I'm excited to share that koog-spm - our Swift Package Manager distribution for Koog—is now public! 🎉 We'd love to hear your feedback if you get a chance to try it out.
K 6
swift 5
Couple of side notes: • releases of
koog-spm
will happen shortly after regular Koog releases • we have some ideas on improving this further, for example by providing more mobile-friendly modules (as discussed in the thread above) • if you have any ideas and feature requests - please use issue tracker in main Koog repo, write on this channel or message me directly