Kakao if(kakao)26: Kanana Space + Kanvas turn KakaoTalk into an agentic interface; closed beta from December

Context

Messaging apps own high-frequency relationships and payments but rarely act as agent schedulers. At if(kakao)26 (2026-10-13), Kakao cast KakaoTalk (~50M users) as an integrated agentic interface—intent and execution inside existing chat/service flows, not a separate chatbot tab. Distribution stays in Talk; owned, partner, and third-party agents become a new surface, with personalization memory and payment governance as hard gates.

Architecture

Kanana Space (two-finger swipe, Ryan persona): messaging, schedules, search, settings now; later commerce/gifting/reservations/transfers, with user approval on consequential acts. Pre-registration opened Oct 13; closed beta in December. Kanvas: PC agent builder with local memory, scheduled jobs, and per-agent browser sandboxes; small closed beta as early as this year; Talk hub for owned/partner/external-framework agents targeted H1 2027. Stack: Kanana-o omni; an AI conductor routes on-device vs large models and tools by complexity; Project Mosaic shares consented memory across Talk/Space/Kanvas. Encoder/decoder are planned open-source—not yet a public repo.

Benchmarks

Public materials are keynote demos and roadmap. No reproducible agent leaderboard (SWE-bench/WebArena-class) was published with the launch. A vendor stage claim cites ~1.6× Korean tokenizer efficiency vs “competing global models” without a fixed public baseline. Treat this as product direction, not GA performance.

Developer path

Follow if.kakao.com/2026 and Kakao Tech. Watch Kanvas tool contracts and sandbox boundaries for Korea-market agents; wait for public API/SDK before assuming callable Agent APIs. Focus engineering reviews on payment confirmation UX, Mosaic consent scopes, and conductor cost routing.