Kakao's Kanana-2-v-decide Is a Decision Model, Not a Chatbot
Nothing here is sponsored — no affiliate links on this page. This breaking article is not the daily buyer-intent post. Facts below come from the sources listed at the end, checked 6 November 2026. We have not tested Kanana-2-v-decide hands-on, and nothing here is a hands-on finding.
Here's a number worth sitting with: every agent you build makes dozens of small decisions per task. Which tool do I call next? Is this search result the right one? How confident am I in that classification? And every single one of those decisions, today, usually costs a full LLM call — a model generating sentences just so you can parse a yes out of them.
Kakao shipped something on 6 November 2026 that skips that whole dance. It's called Kanana-2-v-decide, it's open source on Hugging Face under the Kanana Open License (commercial use allowed), and it doesn't generate text at all. You give it a state — text, JSON, a chat history, optionally images — and a question, and it hands you back a probability, a choice, or a score. That's it. That's the whole product.
🔍 How we put this together
We verified the story against the Seoul Economic Daily, eDaily and Korea Herald Business launch reports (6 November 2026) and the public Hugging Face model card, all listed at the end. We have not run the model hands-on, so nothing here is a hands-on finding. Where a fact is a vendor claim, we say so plainly instead of presenting it as an independent result.What it actually is
Kanana-2-v-decide is a multimodal decision model built on Kakao's own Kanana-2-v-3b. The model card on Hugging Face (kakaocorp/kanana-2-v-decide-3b-2611) puts it plainly: given an input, it answers typed questions — pick one of several options (choice), answer yes or no (noul), or rate on an ordered scale (score) — and returns a probability for each possible answer. It does not generate text.
Under the hood it's an embedding model, not a generator. Each question gets encoded together with the input state into one embedding; each candidate answer gets encoded into another; a softmax over the cosine similarities between them gives you the answer distribution. That's why it's fast: there's no token-by-token generation, just a similarity comparison.
The specs, as published:
- 3.67B parameters — vision encoder 0.49B, language model 3.18B
- Inputs: text, JSON, or chat messages; up to 10 images; up to 20,480 tokens
- Questions: choice, noul, score — any number per request
- License: Kanana Open License — research and commercial use allowed
Kakao's first internal uses are telling: web search and product-category classification. The reported use cases are classifying customer inquiries, identifying products in images, and helping AI agents choose tools. In other words, the boring judgment calls that sit between the interesting parts of an agent's work.
The speed claim, and what it actually means
Kakao says the model averaged under 0.04 seconds per response on a single NVIDIA H200 GPU, and that this is about 43 times faster than GPT-6 Luna, the model it compared against. Those are Kakao's numbers, from Kakao's own measurements — nobody independent has reproduced them yet, and the 43x figure is a comparison against one specific model, not against every LLM you'd use for the same job.
Still, the direction of the claim is the interesting part, and it's easy to check the intuition yourself. If your agent makes, say, 30 routing or classification decisions in a single task and each one costs a 1–2 second LLM call, you're paying 30–60 seconds of pure decision latency — before the agent does anything the user actually asked for. A 0.04-second decision step turns that tax into about a second. That's the difference between an agent that feels instant and one that feels like it's thinking about whether to think.
That's also why the comparison matters less than the architecture. Even if the real-world number is 0.1 seconds instead of 0.04, or 10x faster instead of 43x, a model that returns a probability distribution instead of a paragraph is structurally cheaper for this job. You're not paying generation costs for an answer you were going to parse into a boolean anyway.
The benchmark numbers, with the caveats attached
Kakao reports the highest scores among the models it compared on two evaluation sets:
| Evaluation | Kanana-2-v-decide score | What it is |
|---|---|---|
| Kanana Decision Bench (text) | 72.50 | Kakao's own set of 15,909 Korean-language questions — 18 points ahead of the next-best model compared |
| Decision Index (public) | 61.34 | Publicly available decision benchmark |
| Decision Index Vision | 61.12 | Public vision-decision benchmark |
| Average across the two public sets | 61.23 | Highest average among the models compared |
The comparison group included Microsoft Decision-1, Typesafe AI Zev, and Upstage Solar Decide, per the launch coverage.
Read that table like a sceptic. The 72.50 on Kanana Decision Bench is Kakao's own benchmark, in Korean, and the 18-point lead is against models Kakao chose to compare. The public Decision Index numbers are the ones that matter more, because anyone can check them — and there the lead is real but narrower. The honest read: this looks genuinely competitive on decision tasks, and the Korean-language strength is the part to trust least until someone outside Kakao runs the same tests.
Where this fits in an agent you're actually building
Here's the practical translation. A decision model slots into the gaps in your agent loop — the places where you're currently calling a big model and asking it to answer in JSON so you can extract a field:
- Tool selection. Instead of prompting a model with "which of these 12 tools should I use?" and parsing the reply, you ask the decision model to score each option. One call, a distribution back, no parsing.
- Routing and triage. Classify the incoming request — support, billing, bug report, sales — with a probability attached, so you can set a confidence threshold and escalate the uncertain ones to a human instead of guessing.
- Verification steps. After a tool returns a result, ask: does this satisfy the original request, yes or no? That's a noul question, and it's the cheapest guardrail in an agent loop.
- Scoring and ranking. Rate candidate outputs on an ordered scale instead of asking a model to write a review of its own work.
None of this replaces your main model. It replaces the small, expensive calls you make around your main model — the ones that add latency and cost without adding intelligence.
The limits — stated plainly
- No independent verification yet. Every speed and benchmark number in this article is Kakao's own disclosure. The 43x claim, the 0.04-second average, the benchmark leads — all of it is vendor-reported until someone else reproduces it.
- The headline benchmark is Kakao's own, in Korean. Kanana Decision Bench is 15,909 Korean-language questions. If your agent works in English, the public Decision Index numbers are the more relevant signal, and they're good but not dramatic.
- It's a Korean company's model, and its first deployments are Kakao's own products. Web search and product categorization inside Kakao is the proving ground so far. The open-source release is day one for everyone else.
- 3.67B parameters is small — and that's the point, but also the ceiling. This is a specialist, not a generalist. It won't reason about your problem, write your code, or explain its decisions. If you need explanations, you still need a generative model next to it.
- Nothing here is hands-on. The model hasn't been run for this article, and no latency or accuracy figure here is our measurement. The Hugging Face repo is public — the fastest way to check Kakao's claims is to run the thing yourself.
The bottom line is a measured one. Most of the agent stack is built on the assumption that every judgment needs a full language model. Kanana-2-v-decide is a bet that it doesn't — that a small embedding model returning probabilities is the right tool for the decisions that sit between the real work. If the numbers hold up under independent testing, the agents you already run get noticeably faster and cheaper, because the decision tax quietly disappears. If they don't, it's still a useful pattern to steal: stop paying generation prices for yes-or-no answers.
Where in your agent loop are you currently parsing a paragraph to get a boolean? That's the call this model is trying to replace.
Sources: Seoul Economic Daily, "Kakao Releases AI Decision Model for Faster Agent Judgments" (6 November 2026); eDaily, "Kakao Unveils Agent AI Model Specialized in 'Judgment'... '43 Times Faster Than GPT-6'" (6 November 2026); The Korea Herald Business, "Kakao releases AI decision model 43 times faster than GPT-6 Luna" (6 November 2026); Hugging Face model card, kakaocorp/kanana-2-v-decide-3b-2611. All facts come from the launch-day reporting and the public model card, checked 6 November 2026. No hands-on testing was performed for this article. This breaking article is not the daily buyer-intent post, and it contains no affiliate links.