clawchat-core

ClawChat Core

Use only clawchat-connect tool call; do not construct direct HTTP requests, open another WebSocket, or register MCP tools.

Workflow

1. Read references/tools.md when selecting a tool or constructing its JSON input.

2. Use exact IDs from the authoritative ClawChat turn context or a prior tool result. Never infer an ID from a display name.

3. Require explicit user intent before profile changes, friend mutations, leaving a group, publishing/deleting/reacting/commenting on moments, or app registration changes.

4. Invoke:

   clawchat-connect tool call <tool-name> --input-json '<json>'
   

   The binding is selected from CLAWCHAT_CONNECT_AGENT_ID; do not pass --agent unless intentionally targeting another configured binding.

5. Parse the single JSON stdout record. Treat any nonzero exit or state other than succeeded as failure. Do not retry. A deliberate retry must use a new request ID.

For JSON containing shell-sensitive text, pipe it through stdin:

printf '%s' '<json>' | clawchat-connect tool call <tool-name> --input-json -

Message rules

• For mentions, put visible labels in mentions[].display, not in text.
• For reactions, always pass the exact targetMessageId and chatType from turn context or a prior result.
• After a successful mention or reaction that fully answers a group-turn request, return exactly <clawchat:no-reply/> instead of emitting a duplicate ordinary reply. Never use this signal in a direct conversation.
• Use clawchat_leave_group only with a concrete group conversationId.

Exclusions

Do not use or invent tools for memory, metadata synchronization, get_conversation, or Liveware login. Use $clawchat-liveware for creating and tunneling a new Liveware app.