pi-onlyne 0.3.0 → 0.3.1

package/README.md

@@ -70,7 +70,7 @@ export ONLYNE_BIN=/path/to/onlyne
 /onlyne watch on
 ```
 
-When a message arrives through Onlyne, pi receives it as a follow-up message. The agent can then call `onlyne_reply`, or deliberately call `onlyne_mark_no_reply`.
+When a normal user message arrives through Onlyne, pi receives it as a follow-up message. Onlyne control messages such as `/handshake` are consumed silently. The agent can then call `onlyne_reply`, or deliberately call `onlyne_mark_no_reply`.
 
 ## Commands
 
@@ -118,7 +118,7 @@ onlyne_broadcast({
     { channelId: "telegram" },
     { channelId: "feishu" }
   ],
-  text: "# Release shipped\n\nVersion 0.3.0 is live."
+  text: "# Release shipped\n\nVersion 0.3.1 is live."
 })
 ```
 

package/SPEC.md

@@ -15,6 +15,7 @@ Pi extension for Onlyne. Onlyne remains a workspace-local IM broker; this extens
 - Send tools default to Markdown and may pass `raw_text: true` to Onlyne for literal text.
 - Broadcast sends concurrently with per-target retry and per-target results.
 - Loopback inbound messages wake Pi without creating a reply obligation.
+- `/handshake` inbound messages are Onlyne control messages and must not be surfaced to Pi as agent work.
 - After pi surfaces an inbound follow-up, it calls `mark_io_consumed` so Onlyne FIFO `out_cursor = "consume"` stays synchronized with pi notifications.
 - FIFO IO itself remains owned by the Onlyne daemon; pi-onlyne does not open `.onlyne/channels/*/in|out` directly.
 

package/dist/index.js

@@ -18,6 +18,9 @@ async function startWatch(pi) { state.workspace = findWorkspace(state.cwd); if (
         pi.sendUserMessage(`Onlyne loopback activation${inbound.conversationId ? ` (${inbound.conversationId})` : ""}:\n\n${inbound.text}`, { deliverAs: "followUp" });
     consumeIfNotified(inbound);
     return;
+} if (inbound.text.trim() === "/handshake") {
+    consumeIfNotified(inbound);
+    return;
 } state.currentInbound = { ...inbound, replied: false, noReply: false, reminders: 0 }; if (mode === "auto-handle") {
     pi.sendUserMessage(`Onlyne inbound message from ${inbound.channelId}/${inbound.conversationId}:\n\n${inbound.text}\n\nReply with onlyne_reply, or call onlyne_mark_no_reply if no reply is needed.`, { deliverAs: "followUp" });
     consumeIfNotified(inbound);
@@ -29,7 +32,7 @@ async function reply(text) { if (!state.workspace)
     throw new Error("no active inbound message"); const res = await sendWithRetry(state.workspace.socketPath, { channelId: inbound.channelId }, text, currentConfig().outbound.retry.attempts); if (res.ok)
     inbound.replied = true; return res; }
 export default function onlyne(pi) {
-    pi.on("session_start", async (_event, ctx) => { state.cwd = ctx.cwd; state.workspace = findWorkspace(ctx.cwd); ctx.ui.setStatus("onlyne", state.workspace ? "onlyne: ready" : "onlyne: no .onlyne"); if (currentConfig().watch.autoStart && state.workspace) {
+    pi.on("session_start", async (_event, ctx) => { const resumeWatch = state.watching; stopWatch(); state.cwd = ctx.cwd; state.workspace = findWorkspace(ctx.cwd); state.currentInbound = undefined; state.lastValidOutput = undefined; ctx.ui.setStatus("onlyne", state.workspace ? "onlyne: ready" : "onlyne: no .onlyne"); if ((currentConfig().watch.autoStart || resumeWatch) && state.workspace) {
         try {
             ctx.ui.notify(await startWatch(pi), "info");
         }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-onlyne",
-  "version": "0.3.0",
+  "version": "0.3.1",
   "description": "Pi extension tools for sending messages through Onlyne.",
   "type": "module",
   "main": "./dist/index.js",