feat: Koog → Aigentic Platform run-publishing proof-of-concept

[nsmnds]

What & why

Investigates whether JetBrains Koog can be made to publish its agent runs to the Aigentic Platform using the same contract Aigentic itself uses, and provides a working proof-of-concept.

Answer: yes — and no fork/patch of Koog is needed. This was verified against the real Koog 1.0.0 source, not guessed.

How Aigentic publishes a run (the contract we target)

After every run, publishRun (src/core/.../agent/AgentExecutor.kt) makes a single authenticated request when a platform { … } is configured:

POST RunDto  ->  /gateway/runs        (HTTP Basic Auth; 201 / 401 / 400 / 500)

RunDto (src/platform/wirespec/gateway.ws) carries startedAt/finishedAt, config (task, model identifier, system prompt, tools, temperature…), result (Finished/Stuck/Fatal), messages[], and modelRequests[] (per-LLM-call token usage). Publishing is not runtime-specific — it is just "build a RunDto and POST it".

How the PoC mirrors it from Koog

Koog's agents-features-event-handler exposes the full lifecycle via handleEvents { … }. A small aigenticPlatform(name, secret, …) extension installs it, collects the run, and POSTs a RunDto on completion — the Koog-side equivalent of publishRun:

val agent = AIAgent(promptExecutor = executor, llmModel = model, systemPrompt = "…") {
    aigenticPlatform(name = "…", secret = "…")   // publishes the run on completion
}
agent.run("…")

Hooks used: onAgentStarting, onLLMCallStarting/onLLMCallCompleted (full Prompt, LLModel, tool descriptors, the Message.Assistant response + its token counts → modelRequests), and onAgentCompleted/onAgentExecutionFailed (→ Finished/Fatal result + POST).

What's included

• PlatformRunDto.kt — DTOs mirroring gateway.ws.
• KoogRunMapper.kt — maps Koog Message/MessagePart/ToolDescriptor → Aigentic DTOs.
• AigenticPlatformExporter.kt — the aigenticPlatform(...) EventHandler exporter.
• AigenticPlatformExporterTest.kt — runs a real Koog agent (LLM mocked via getMockExecutor, platform mocked via Ktor MockEngine) and asserts exactly one RunDto POSTed to /gateway/runs containing the system prompt, the assistant response, a modelRequests entry, and a FinishedResultDto. ✅ passing.

./gradlew -p poc/koog-platform test

Important: why this is an isolated build

Koog 1.0.0 is built with Kotlin 2.3.10; Aigentic is on Kotlin 2.1.10. Kotlin metadata is not forward-compatible, so the main (2.1.10) build cannot compile against Koog's artifacts. The PoC is therefore a standalone Gradle build under poc/koog-platform/ (its own settings.gradle.kts, Kotlin 2.3.10), is not wired into the root build, and does not affect ./gradlew build. PlatformRunDto.kt reproduces the contract locally for the same reason.

A production integration would reuse the Wirespec-generated RunDto/Gateway client from the published community.flock.aigentic:platform artifact (readable by a Kotlin ≥ 2.3 consumer) or align the two projects' Kotlin versions.

See poc/koog-platform/README.md for full details.

---

Generated by Claude Code