chats / members / chatinfo

chats

List chat rooms. By default this uses LOCO and gives you the broader chat list surface.

openkakao-rs chats [OPTIONS]

[!NOTE] chats is now LOCO-first. Add --rest only when you explicitly want the old recent-cache view from the desktop app.

Choose default chats when you want:

• the broader server-backed chat list
• consistency with read, send, and watch
• a better signal for whether LOCO session health is intact

Choose chats --rest when you want:

• quick unread/account-adjacent views
• lower session overhead
• data that is already present in the Pilsner cache

loco-chats (legacy)

loco-chats remains available as a hidden compatibility command, but new usage should move to chats.

openkakao-rs loco-chats [--all]

members

List members in a chat room. By default this uses LOCO and falls back to REST if the LOCO request fails.

openkakao-rs members <chat_id> [--full] [--rest]

Use default members when you want:

• membership data from the active LOCO session
• behavior aligned with other chat-surface commands
• a stricter signal that the messaging session is still valid

Use members --rest when you explicitly want:

• the older REST member list path
• a cheaper one-shot lookup when LOCO is not the target

Use members --full when you want:

• richer GETMEM profile fields from LOCO
• status message and profile image metadata
• a better basis for chat-scoped profile inspection

loco-members remains available as a hidden compatibility command.

chatinfo

Get detailed information about a chat room.

openkakao-rs chatinfo <chat_id>

Returns raw LOCO CHATONROOM response with metadata, settings, and member count.

Use 0 as chat_id to find/create MemoChat (chat with yourself).

loco-chatinfo remains available as a hidden compatibility command.

MemoChat

MemoChat (나와의 채팅) is your private chat-with-yourself room. It is useful for testing sends, storing notes, and verifying automation pipelines without touching real conversations.

MemoChat does not appear in the default LOCO LCHATLIST response, so it won't be listed by the plain chats command or by chats --type memo (the filter applies after the fetch). The chats --rest path may include MemoChat if it is present in your Pilsner cache. For a reliable way to find or create MemoChat, use chatinfo with id 0:

openkakao-rs chatinfo 0

This issues a LOCO CREATE command with memberIds: [] and memoChat: true. If a MemoChat already exists for your account, the server returns its chatId. If not, it creates one.

Once you have the MemoChat chatId, you can use it with read, send, watch, and other chat-scoped commands like any other room:

# Read MemoChat messages
openkakao-rs read <memo_chat_id>

# Send a test message to MemoChat
openkakao-rs send <memo_chat_id> "test message" -y

MemoChat is the safest target for testing outbound automation before pointing it at real conversations.

profile (chat-scoped LOCO)

profile can point at a specific chat and reuse LOCO GETMEM.

openkakao-rs profile <user_id> --chat-id <chat_id>

Use this when you already know the chat and want:

• profile reads without depending on the REST friend profile path
• the same member metadata that members --full exposes
• a stricter signal that the active LOCO session is healthy

If you do not know the right chat, you can also resolve from the local LOCO graph:

openkakao-rs profile <user_id> --local

This scans known chats and merges GETMEM results into a partial graph. It is slower than --chat-id, but it can still resolve users that have already appeared somewhere in your LOCO-visible chat set.

When you run plain profile <user_id>, OpenKakao still tries the REST friend profile path first. If that fails, it automatically falls back to the local LOCO graph before giving up.