openclaw-opencode-bridge 2.0.8 → 2.0.9

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openclaw-opencode-bridge",
-  "version": "2.0.8",
+  "version": "2.0.9",
   "description": "Bridge OpenClaw messaging channels to OpenCode via tmux persistent sessions",
   "main": "./lib/onboard.js",
   "bin": {

package/templates/scripts/opencode-session.sh

@@ -1,11 +1,12 @@
 #!/bin/bash
-# bridge-version: 4
-# Keep OpenCode server alive (runs every 30s via daemon)
-# Safe: idempotent, flock-protected (with fallback)
+# bridge-version: 5
+# Keep OpenCode server running in background (for faster message processing)
+# Daemon runs every 30s to ensure server stays alive
 
 OPENCODE="{{OPENCODE_BIN}}"
 WORKSPACE="{{WORKSPACE}}"
 LOCK_FILE="/tmp/opencode-session.lock"
+PID_FILE="/tmp/opencode-session.pid"
 TIMEOUT=10
 
 # Use flock for lock protection if available
@@ -25,10 +26,17 @@ fi
 
 cd "$WORKSPACE"
 
-# Start OpenCode in server mode if not running
-if ! pgrep -f "opencode serve" > /dev/null 2>&1; then
-    "$OPENCODE" serve &
-    sleep 2
+# Check if server is already running
+if [ -f "$PID_FILE" ]; then
+    OLD_PID=$(cat "$PID_FILE")
+    if [ -n "$OLD_PID" ] && kill -0 "$OLD_PID" 2>/dev/null; then
+        exit 0
+    fi
 fi
 
+# Start OpenCode server in background
+nohup "$OPENCODE" serve > /tmp/opencode-serve.log 2>&1 &
+echo $! > "$PID_FILE"
+sleep 3
+
 exit 0

package/templates/workspace/OPENCODE.md

@@ -2,23 +2,33 @@
 
 ## Bot Mode
 
-When a message starts with `[{CHANNEL}:{ID}]` prefix, you **MUST** follow this procedure.
+When a message starts with `[{CHANNEL}:{ID}]` prefix, you are being used as a bot.
+
+### Message Format
+
+The format is: `[CHANNEL:ID] actual message`
+
+**Examples:**
+- `[telegram:850961516] hello` → Channel=telegram, ID=850961516, Message="hello"
+- `[discord:123456] build a website` → Channel=discord, ID=123456, Message="build a website"
+
+**IMPORTANT:** The prefix `[channel:id]` is metadata. You should ONLY respond to the actual message, NOT repeat the prefix or the user's name in your response.
 
 ### Procedure
 
-1. Extract `{CHANNEL}` and `{ID}` from the prefix
-2. Perform the task described after the prefix
-3. **After completion, send the response via:**
+1. Extract `{CHANNEL}` and `{ID}` from the `[...]` prefix
+2. Ignore everything before `] ` — that is the prefix, not the message
+3. Perform the task described in the actual message
+4. **After completion, send the response via:**
 ```bash
-openclaw message send --channel {CHANNEL} --target {ID} -m '🔗 response'
+openclaw message send --channel {CHANNEL} --target {ID} -m '🔗 your response here'
 ```
-4. **Every message MUST start with 🔗** — this identifies you as OpenCode
-5. Split messages over 4000 characters into multiple sends (each starts with 🔗)
+5. **Every message MUST start with 🔗** — this identifies you as OpenCode
+6. Split messages over 4000 characters into multiple sends (each starts with 🔗)
 
 ### Response transmission is mandatory (never skip)
 
-- **Every `[{CHANNEL}:{ID}]` message MUST receive a response via the channel.**
-- Regardless of success, failure, or error, you must always send the result.
-- Ending a turn without sending is **strictly forbidden**.
+- **Every message MUST receive a response.**
+- Ignore the prefix, only respond to the actual message content.
 - If the task failed, send the failure reason. If it succeeded, send the result.
 - If you did not run `openclaw message send`, the task is **NOT** complete.