u-foo 3.0.11 → 3.0.13

package/SKILLS/ubus/SKILL.md

@@ -1,18 +1,19 @@
 ---
 name: ubus
 description: |
-  Poll event bus, check pending messages.
-  Use when: (1) check if other Agents sent messages, (2) view bus status, (3) periodic polling.
+  Check and handle pending event-bus messages when /ubus is explicitly invoked.
+  Use when: (1) asked to check messages, (2) view bus status, (3) use watch/listen/auto modes.
   If not yet joined bus, will auto-join.
 ---
 
-# /ubus - Event Bus Polling
+# /ubus - Check Event Bus Messages
 
-Check pending messages on the event bus.
+Check and handle pending messages on the event bus when `/ubus` is explicitly
+invoked.
 
 ## Arguments
 
-- `/ubus` - Check messages and show status
+- `/ubus` - Pull pending messages and show status
 - `/ubus watch` - Start background auto-notification (title badge + bell + notification center)
 - `/ubus stop` - Stop background auto-notification
 - `/ubus listen` - Foreground continuous listener, print new messages (suitable for side terminal)
@@ -74,7 +75,7 @@ If argument is `listen`, foreground blocking listener (no background task tool n
 ufoo bus listen "$SUBSCRIBER" --from-beginning
 ```
 
-If argument is `auto`, unattended auto-execute:
+If argument is `auto`, use unattended auto-execute:
 
 ```bash
 # Start daemon (background resident), auto-inject /ubus + Enter on new message
@@ -118,7 +119,8 @@ After you have read and processed the messages, you MUST acknowledge them to pre
 ufoo bus ack "$SUBSCRIBER"
 ```
 
-**This is critical** - if you don't ack, the daemon will keep injecting `/ubus` commands.
+**This is critical** - if you don't ack, the runtime may retry delivery or keep
+the event pending.
 
 **Default behavior is ack-only, no reply.** If there's nothing to do (no actionable task, no question to answer, no follow-up the sender genuinely needs), just ack and stop. Silence is a valid response — see "Handling Received Messages" below for when a reply IS warranted.
 
@@ -196,11 +198,15 @@ and the two of you will ping-pong forever.
 | `这个 bug 的根因是什么？` (question) | ✅ reply with answer |
 | `我帮你找到了 X，需要你做 Y` (request) | ✅ reply with status |
 
-When in doubt: ack and wait. If the sender genuinely needs something
-from you, they will follow up with a concrete question or task.
+When in doubt: ack and stop. If the sender genuinely needs something from you,
+they will follow up with a concrete question or task.
 
 ## Sending Messages
 
+After sending a message, do not run `/ubus`, poll, sleep, or wait for a reply.
+Continue the current task. Any follow-up message will be automatically injected
+into your prompt/session.
+
 ### Smart Routing (when you don't know the target ID)
 
 If the user says "notify codex to do X" without specifying an ID, use smart routing:

package/SKILLS/ufoo/SKILL.md

@@ -117,11 +117,21 @@ ufoo memory audit mem-0001
 
 ## 3. Event Bus (ubus)
 
+### Delivery Rule
+
+After `ufoo bus send` or `ufoo bus broadcast`, do not run
+`ufoo bus check`, invoke `/ubus`, sleep, or wait for a reply. Continue the
+current task. Any follow-up message will be automatically injected into your
+prompt/session.
+
+When `/ubus` is explicitly requested, follow its pending-message flow
+immediately. Do not invoke it merely to wait for a reply to a message you sent.
+
 ### Commands
 
 ```bash
-ufoo bus check "$UFOO_SUBSCRIBER_ID"        # Check pending messages
-ufoo bus ack "$UFOO_SUBSCRIBER_ID"           # Acknowledge after handling
+ufoo bus check "$UFOO_SUBSCRIBER_ID"        # Used by an explicit /ubus request
+ufoo bus ack "$UFOO_SUBSCRIBER_ID"          # Acknowledge after handling
 ufoo bus send "<target>" "<message>"         # Send message
 ufoo bus broadcast "<message>"               # Broadcast to all
 ufoo bus status                              # Show bus status
@@ -149,13 +159,13 @@ Notes:
 - Type: `codex` (all codex agents)
 - Wildcard: `*` (broadcast)
 
-### CRITICAL: When you receive pending messages
+### CRITICAL: When a message is received
 
 **EXECUTE tasks immediately. Do NOT ask the user.**
 
-1. Check: `ufoo bus check $UFOO_SUBSCRIBER_ID`
-2. Execute each task
-3. **Always ack**: `ufoo bus ack $UFOO_SUBSCRIBER_ID`
+1. Read the available `[ufoo]<from:...>` message.
+2. Execute each task.
+3. **Always ack after handling**: `ufoo bus ack $UFOO_SUBSCRIBER_ID`
 4. Reply only when substantive — send `ufoo bus send "<publisher>" "<result>"` only if:
    - The sender asked a question → reply with the answer
    - The sender delegated a task → reply with the result / artifact
@@ -164,6 +174,10 @@ Notes:
 5. **Report** if the work arrived from `[manual]<to:...>` or `[ufoo]<from:...>`:
    `ufoo report progress|done|error "<short summary>"`
 
+If `/ubus` is explicitly requested, run
+`ufoo bus check "$UFOO_SUBSCRIBER_ID"` and then follow the same execute → ack
+flow.
+
 ---
 
 ## 4. Message Format

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "u-foo",
-  "version": "3.0.11",
+  "version": "3.0.13",
   "description": "Multi-Agent Workspace Protocol. Just add u. claude → uclaude, codex → ucodex.",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://ufoo.dev",

package/src/agents/prompts/groupBootstrap.js

@@ -40,6 +40,10 @@ const SHARED_UFOO_PROTOCOL = [
   "",
   "`ufoo bus send <target> \"<message>\"`",
   "",
+  "After sending, do not poll `ufoo bus check`, invoke `/ubus`, sleep, or wait",
+  "for a reply. Continue the current task; any follow-up message will be",
+  "automatically injected into your prompt/session.",
+  "",
   "On received bus work: execute it, then `ufoo bus ack \"$UFOO_SUBSCRIBER_ID\"`.",
   "Reply only if you have a concrete result, answer, or follow-up the sender",
   "needs. Default is ack-only; silence is a valid response.",

package/src/agents/prompts/native/ufoo.js

@@ -9,11 +9,13 @@ Participate in multi-agent coordination through the ufoo bus/context system:
 - Use shared memory for durable project facts. Read existing memory before writing new memory; do not use it for transient task state.
 - Support launch/close/resume/inject flows managed by ufoo daemon.
 - Prefer canonical ufoo commands (\`ufoo ctx\`, \`ufoo bus\`, \`ufoo memory\`, \`ufoo report\`) for coordination and status sync.
+- After sending a bus message, do not poll \`ufoo bus check\`, invoke \`/ubus\`, sleep, or wait for a reply. Continue the current task; any follow-up message will be automatically injected into your prompt/session.
 
 Execution protocol:
 - On session start, check context quickly:
   \`ufoo ctx decisions -l\`
   \`ufoo ctx decisions -n 1\`
+- If \`ubus\` is explicitly requested, execute its pending-message flow immediately; this does not change the no-polling rule after you send a message.
 - After handling work that arrived from chat (\`[manual]<to:...>\`) or bus (\`[ufoo]<from:...>\`), report lifecycle:
   \`ufoo report start|progress|done|error "<short summary>"\`
   Do not emulate report failures with \`ufoo bus send ufoo-agent ...\`; if \`ufoo report\` fails, continue without a fallback bus report.

package/src/code/UCODE_PROMPT.md

@@ -17,11 +17,13 @@ ufoo integration requirements:
 - Use shared memory for durable project facts. Read existing memory before writing new memory; do not use it for transient task state.
 - Support launch/close/resume/inject flows managed by ufoo daemon.
 - Prefer canonical ufoo commands (`ufoo ctx`, `ufoo bus`, `ufoo memory`, `ufoo report`) for coordination and status sync.
+- After sending a bus message, do not poll `ufoo bus check`, invoke `/ubus`, sleep, or wait for a reply. Continue the current task; any follow-up message will be automatically injected into your prompt/session.
 
 Execution protocol:
 - On session start, check context quickly:
   `ufoo ctx decisions -l`
   `ufoo ctx decisions -n 1`
+- If `ubus` is explicitly requested, execute its pending-message flow immediately; this does not change the no-polling rule after you send a message.
 - After handling work that arrived from chat (`[manual]<to:...>`) or bus (`[ufoo]<from:...>`), report lifecycle:
   `ufoo report start|progress|done|error "<short summary>"`
   Do not emulate report failures with `ufoo bus send ufoo-agent ...`; if `ufoo report` fails, continue without a fallback bus report.