Getting Started
The shortest path from install to a real chat read.
Introduction
This path is intentionally narrow: install, authenticate, inspect a chat, then stop and evaluate whether the trust model fits your use case.
Install the CLI
Start with a local binary and keep the workflow on your own machine.
Authenticate once
Reuse a saved local login before you build any higher-level automation.
Inspect chats first
List chats and read a small slice before you design summaries, exports, or hooks.
Send only if needed
Outbound actions should come last, after you understand the trust and transport boundary.
Before you wire automation
If you are deciding between account checks and real chat access, read REST vs LOCO before building around watch, send, or media flows.
Account risk is real
Depending on how you use OpenKakao, Kakao may interpret that behavior as a violation of its Terms of Service or operating policies. That can lead to account restrictions, suspension, or permanent deletion.
Automatic Installation
brew tap JungHoonGhae/openkakao
brew install openkakao-rsAuthenticate
Make sure KakaoTalk is running and already logged in.
openkakao-rs login --save
openkakao-rs authInspect a Real Chat
List chats first:
openkakao-rs chatsThen read only a small slice:
openkakao-rs read <chat_id> -n 20Export Before You Automate
Move one read into a structured format before you connect other tools:
openkakao-rs read <chat_id> -n 20 --json | jq '.'Send Only If You Need It
openkakao-rs send <chat_id> "Hello from CLI!"Default prefix stays on for a reason
By default, sent messages include a visible prefix. Keep that behavior unless you have a strong reason not to and you fully understand the operational risk.