Introduction
Developer docs for bringing KakaoTalk into local workflows on macOS.
Introduction
OpenKakao is a beta-stage unofficial KakaoTalk CLI for macOS for developers, terminal-native users, and automation-heavy workflows. It opens a usable local surface around chats, history, watch events, and controlled outbound actions.
OpenKakao is most useful when you need a narrow local bridge between KakaoTalk and tools you already control.
Read and structure chat context
Inspect message history, unread state, and chat metadata before you automate anything else.
Trigger local workflows
Use watch mode, hooks, and webhooks to connect KakaoTalk events to scripts, queues, and operator tools.
Send carefully
Keep outbound actions explicit, reviewable, and easy to narrow when automation starts touching real chats.
Know the trust boundary
Understand what is read locally, what is stored, and where privacy and account-safety assumptions change.
Want to evaluate fit first?
Start with Automation Overview if you are deciding whether OpenKakao fits your workflow. Move to Trust Model once you need the risk boundary.
Start Here
Use Cases
Where OpenKakao becomes useful in real workflows.
Getting Started
Install, authenticate, and read a chat in a few minutes.
Security
What the CLI touches, stores, and where the risks are.
CLI Reference
Command-by-command reference for real usage.
REST vs LOCO
Decide which transport fits which task.
Protocol Notes
Deeper technical notes on LOCO and transport behavior.
Where It Helps
OpenKakao is strongest when you need one of these outcomes:
- turn unread chats into summaries, dashboards, or review queues
- export message history into JSON, SQLite, or local search tools
- trigger local scripts or webhooks from watch events
- use KakaoTalk as an input channel for operator tools, LLMs, or agents
- move careful outbound actions into a controlled local workflow
Working Model
flowchart LR
A[KakaoTalk macOS app] -->|Cache and app state| O[openkakao-rs]
O -->|REST calls| K[katalk.kakao.com]
O -->|REST calls| P[talk-pilsner.kakao.com]
O -->|LOCO TCP plus BSON| L[booking and ticket and LOCO servers]
O -->|JSON output| T[Shell scripts, jq, sqlite, LLM tools]Use the transport boundary as a rule of thumb:
- REST for fast account checks and cache-backed reads
- LOCO for real chat workflows, watch mode, media, and sending
Keep the model small
OpenKakao is not a hosted messaging platform. It is a local bridge for inspecting, structuring, and narrowing automation around a real KakaoTalk session.
Next Paths
- New here: Why OpenKakao
- Ready to try it: Installation
- Need the trust boundary first: Data & Credentials
- Want practical patterns: Common Recipes