openclaw-pine

OpenClaw channel plugin for Pine AI. Let Pine AI contact customer service for you.

Install

openclaw plugins install openclaw-pine

Configuration

Add to your OpenClaw config:

channels:
  pine:
    access_token: "your-pine-access-token"
    user_id: "your-pine-user-id"

Or use the auth tools:

• pine_auth_request — send verification code
• pine_auth_verify — verify code and get credentials

How it works

Pine AI runs as a channel — just like Telegram. The plugin maintains a persistent Socket.IO connection to the Pine AI backend. When Pine AI sends an event (a question, a form, a work log update, an OTP request), it arrives as an inbound message to the agent automatically.

Stream buffering

Text streaming is buffered internally. The agent receives one complete merged message, not individual chunks — avoiding expensive per-chunk LLM calls.

Tools

• pine_create_session — create a new session
• pine_task_start — start task execution (Pro subscription)
• pine_task_stop — stop a running task
• pine_sessions — list, get, or delete sessions
• pine_social_share — share task results on social media (earn credits)
• pine_upload_attachment — upload evidence documents (bills, screenshots)
• pine_send_message — send a message with attachments to a session

Agent behavior: respond, stay silent, or ask the human

Pine AI behaves like a human assistant — it sends acknowledgments, does work, then sends the real response. The agent must NOT reply to every message or it creates an infinite loop.

Respond when Pine AI sends a form, asks a question you can answer, says task_ready, or finishes.

Stay silent when Pine AI sends acknowledgments ("Got it!"), work logs, state changes, or status updates.

Ask the human when Pine AI needs OTP codes, PINs, security answers, scheduling confirmation, or anything not provided. Never hallucinate answers.

See skills/pine-assistant/SKILL.md for the full behavioral rules.

Example flow

User: "Negotiate my Comcast bill down to $50/month"

1. Agent calls pine_create_session
2. Agent sends message through Pine AI channel
3. Pine AI researches, sends work logs (agent stays silent)
4. Pine AI sends a form asking for account details (agent fills it)
5. Pine AI says "task_ready" — agent calls pine_task_start
6. Pine AI executes: calls Comcast, negotiates (agent stays silent)
7. Pine AI may need OTP (agent asks the human, relays code)
8. Task finishes with summary (agent shares with human)

License

MIT