ploop

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Ploop

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
    .
Ploop是本地终端会话与用户移动聊天应用之间的桥梁。
简短模型:
  • 终端会话 = 设备身份。
  • 对话 = 单个用户线程。
  • 应用UI会根据你推送的内容更新:
    status
    、可选的
    step
    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
当任务涉及以下内容时使用本技能:
  • 监听新的Ploop消息
  • 向Ploop对话发送或起草回复
  • 在应用中显示输入/进度状态(
    thinking
    running
    done
    error
  • 在认证/会话问题后恢复停滞的循环

Flows

流程

1) Install + Login + Init

1) 安装 + 登录 + 初始化

If CLI/session is not ready, run
INSTALLATION.md
.
如果CLI/会话未就绪,请运行
INSTALLATION.md

2) Listen For New Messages

2) 监听新消息

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

$PLOOP start --json
One-shot check:
bash
$PLOOP poll --json
推荐的持续循环方式:
bash
if command -v ploop >/dev/null 2>&1; then
  PLOOP="ploop"
else
  PLOOP="npx ploop@latest"
fi

$PLOOP start --json
单次检查:
bash
$PLOOP poll --json

3) React To Each New User Message

3) 响应每条新用户消息

For each incoming item in
messages[]
, follow this exact order:
bash
$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:
bash
$PLOOP status --conversation <conversation_id> --state error
$PLOOP send --conversation <conversation_id> --message "I hit an issue while processing this. I can retry now."
对于
messages[]
中的每个传入项,请严格按照以下顺序执行:
bash
$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
如果执行失败:
bash
$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
    .
  • status thinking
    :当处理不即时时快速发送。
  • step
    :仅发送有意义的里程碑(不要冗余内容)。
  • send
    :最终对用户可见的回复。
  • 终端状态:始终以
    done
    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.
  • 仅使用轮询,不使用流。
  • 保持更新原子性:
    status
    step
    message
  • 如果认证/会话失败,请切换到
    INSTALLATION.md
    进行恢复,然后返回运行时循环。