Ploop

Ploop is a bridge between a local terminal session and the user’s mobile chat app.

Short model:

• Terminal session = device identity.
• Conversation = one user thread.
• The app UI updates from what you push: status, optional step, and message.

When To Use

Use this skill when the task is about:

• listening for new Ploop messages
• sending or drafting replies into Ploop conversations
• showing typing/progress in the app (thinking, running, done, error)
• resuming a stalled loop after auth/session issues

Flows

1) Install + Login + Init

If CLI/session is not ready, run INSTALLATION.md.

2) Listen For New Messages

Preferred continuous loop:

if command -v ploop >/dev/null 2>&1; then
  PLOOP="ploop"
else
  PLOOP="npx ploop@latest"
fi

$PLOOP start --json

One-shot check:

$PLOOP poll --json

3) React To Each New User Message

For each incoming item in messages[], follow this exact order:

$PLOOP status --conversation <conversation_id> --state thinking
$PLOOP step --conversation <conversation_id> --message "<meaningful milestone>"
$PLOOP send --conversation <conversation_id> --message "<final answer>"
$PLOOP status --conversation <conversation_id> --state done

If execution fails:

$PLOOP status --conversation <conversation_id> --state error
$PLOOP send --conversation <conversation_id> --message "I hit an issue while processing this. I can retry now."

What To Push To The App

• status thinking: send quickly when work is not instant.
• step: send only meaningful milestones (not noise).
• send: the final user-visible response.
• terminal status: always end with done or error.

Reliability Rules

• Polling only, no streaming.
• Keep updates atomic: status, step, message.
• If auth/session fails, switch to INSTALLATION.md, recover, then return to runtime loop.