You Built a Kotlin AI Agent. Should You Migrate to Koog?

JetBrains Koog vs Google GenAI SDK — Should You Switch? You've built a working AI agent with Google GenAI. Now JetBrains releases Koog, a Kotlin-first AI framework. Should you migrate? Probably not — here's why. See also: SQLite Embeddings for Local Agents for the RAG implementation referenced in this article. The Problem When building AI agents in Kotlin, you have two main options: Google GenAI SDK — Direct API wrapper, full control, manual tool loop JetBrains Koog — Higher-level framework, Kotlin DSL, built-in agent patterns Both work. The question is: what do you gain and lose by switching? What Koog Offers Koog is JetBrains' attempt to bring Kotlin-native ergonomics to AI agent development. It wraps multiple LLM providers (Gemini, OpenAI, Anthropic) behind a unified DSL. Cleaner Tool Definitions With Google GenAI, tool definitions are verbose: val currentTimeDeclaration = FunctionDeclaration . builder () . name ( "get_current_time" ) . description ( "Get the current date and time"