jbaruch/koog
Koog 1.0 idioms, gotchas, and scaffolding skills for Kotlin agents on the JVM
86
88%
Does it follow best practices?
Impact
86%
1.86xAverage score across 45 eval scenarios
Advisory
Suggest reviewing before use
task.mdevals/scenario-2/
Expose a Koog Agent on an HTTP Endpoint
Problem/Feature Description
A developer has a working Koog 1.0 agent (constructed in a main() with runBlocking). They want to host it behind a Ktor HTTP server — a single POST /agent route that takes the request body as the agent's input, runs the agent, and returns the result as the response body.
They have an existing Ktor Application.module() function in their codebase; they want the agent wired in alongside their other Ktor configuration. Their LLM provider is OpenAI; the API key comes from OPENAI_API_KEY.
Output Specification
Walk through the wiring. Produce the modified Application.module() (or equivalent) and the Gradle dependency change as a single response, labeled.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
scenario-42
scenario-43
scenario-44
scenario-45
skills
add-observability
add-persistence
add-rag
add-structured-output
add-token-budgeting
add-tool
cache-llm-calls
define-prompt
domain-model-subtask-pipeline
references
enable-prompt-caching
handle-agent-events
manage-state
migrate-from-0-x
model-planner-subtasks
persist-chat-history
query-sql-from-agent
scaffold-agent
snapshot-and-restore
test-koog-agents
trace-agent-internals
use-attachments
use-functional-agent
use-llm-node-variants
use-planner
wire-a2a
wire-acp-server
wire-ktor-server
wire-mcp-server
wire-spring-boot