@badgerclaw/connect 1.2.1 → 1.2.2

package/SETUP.md

@@ -122,8 +122,7 @@ When you install BadgerClaw with a fresh pairing code, the plugin automatically
   "groups": {
     "*": {
       "autoReply": true,
-      "enabled": true,
-      "systemPrompt": "You are a helpful AI assistant..."
+      "enabled": true
     }
   }
 }
@@ -132,19 +131,22 @@ When you install BadgerClaw with a fresh pairing code, the plugin automatically
 This means:
 - Bot joins any room it's invited to
 - Bot responds to all messages (no @mention required)
-- Bot uses a helpful assistant personality in groups
+- Bot uses **your OpenClaw workspace personality** (SOUL.md, IDENTITY.md, etc.) in all conversations — groups and DMs alike
 
-### Custom Group Personality
+When the bot joins a new encrypted room, it sends a hint message explaining the `/bot talk on|off` commands so room members know how to control it.
 
-By default, the bot uses a generic helpful assistant prompt in groups — **not** your OpenClaw workspace personality (SOUL.md, IDENTITY.md). This prevents workspace personas from causing the bot to stay silent in groups.
+### Your Personality, Everywhere
 
-To customize the group personality, edit your OpenClaw config:
+BadgerClaw respects your OpenClaw workspace files. If you've configured a custom personality (SOUL.md), the bot uses that personality in groups and DMs. This means:
 
-```bash
-openclaw configure
-```
+- A "pirate assistant" SOUL.md → bot talks like a pirate in groups
+- A "professional COO" SOUL.md → bot acts professional in groups
+- No SOUL.md → bot uses the default helpful assistant behavior
+
+**If your bot stays silent in groups**, your workspace files may include instructions like "stay silent in groups" or "only respond when needed." To fix this:
 
-Or manually edit `~/.openclaw/openclaw.json`:
+1. Edit your SOUL.md to allow group responses, OR
+2. Add a group-specific system prompt override:
 
 ```json
 {
@@ -153,7 +155,7 @@ Or manually edit `~/.openclaw/openclaw.json`:
       "groups": {
         "*": {
           "autoReply": true,
-          "systemPrompt": "You are Captain Bot, a pirate AI. Answer in pirate speak."
+          "systemPrompt": "You are a helpful AI assistant. Always respond to messages in group chats."
         }
       }
     }
@@ -183,6 +185,43 @@ You can configure specific rooms differently:
 
 ---
 
+## Upgrading from v1.1.x or Earlier
+
+If you installed BadgerClaw before v1.2.0, your config is missing the group auto-reply settings. The bot may not respond in group chats without @mentions.
+
+**Quick fix — run the update command:**
+
+```bash
+openclaw plugins update @badgerclaw/connect
+openclaw configure
+```
+
+Select BadgerClaw and re-enter a pairing code. The new onboarding will add the missing group config automatically.
+
+**Manual fix — if you don't want to re-pair:**
+
+Add this to your `~/.openclaw/openclaw.json` inside `channels.badgerclaw`:
+
+```json
+{
+  "channels": {
+    "badgerclaw": {
+      "groupPolicy": "open",
+      "groups": {
+        "*": {
+          "autoReply": true,
+          "enabled": true
+        }
+      }
+    }
+  }
+}
+```
+
+Then restart: `openclaw gateway restart`
+
+---
+
 ## FAQ
 
 ### Bot doesn't respond in group chats
@@ -193,13 +232,12 @@ You can configure specific rooms differently:
 
 ### Bot shows typing indicator but never replies
 
-This usually means the bot's system prompt is telling it to stay silent. Check:
-
-1. Your `groups` config has `autoReply: true`
-2. The `systemPrompt` in groups config tells the agent to respond (not stay silent)
-3. If you have a SOUL.md with "stay silent in groups" — the groups `systemPrompt` overrides this, but only if it's set
+Your workspace personality (SOUL.md) may tell the agent to stay silent in groups. BadgerClaw respects your workspace files, so if SOUL.md says "don't respond in groups," the bot won't.
 
-Fix: Run `openclaw configure` and reconfigure BadgerClaw, or manually add the groups config shown above.
+**Fix options:**
+1. Edit your SOUL.md to allow group responses
+2. Add a `systemPrompt` override in `channels.badgerclaw.groups.*` that tells the agent to respond (see Group Chat Configuration above)
+3. Run `openclaw configure` and reconfigure BadgerClaw
 
 ### `/bot talk on` doesn't work
 
@@ -211,15 +249,13 @@ openclaw gateway restart
 
 ### Bot responds with wrong personality
 
-The bot uses your **OpenClaw workspace personality** for DMs (SOUL.md, IDENTITY.md) but uses the **groups systemPrompt** for group chats. To change the group personality, edit `channels.badgerclaw.groups.*.systemPrompt` in your config.
+The bot uses your **OpenClaw workspace personality** (SOUL.md, IDENTITY.md) for both DMs and groups. To set a different personality for groups only, add a `systemPrompt` in `channels.badgerclaw.groups.*` in your config.
 
 ### Bot keeps saying "NO_REPLY" or stays silent
 
-Your workspace files (SOUL.md) may instruct the agent to stay silent in groups. The groups `systemPrompt` should override this. If it doesn't:
+Your workspace files (SOUL.md) instruct the agent to stay silent in groups. BadgerClaw respects your personality — this is intentional.
 
-1. Make sure `groups.*.systemPrompt` is set in your config
-2. The prompt should explicitly say to respond to messages
-3. Restart the gateway after config changes
+**To fix:** Add a `systemPrompt` override to your groups config that tells the agent to always respond. See the "Your Personality, Everywhere" section above. Then restart: `openclaw gateway restart`
 
 ### "Invalid pairing code"
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@badgerclaw/connect",
-  "version": "1.2.1",
+  "version": "1.2.2",
   "description": "BadgerClaw channel plugin for OpenClaw",
   "type": "module",
   "dependencies": {

package/src/matrix/monitor/auto-join.ts

@@ -50,8 +50,15 @@ export function registerMatrixAutoJoin(params: {
       }
 
       logVerbose(`badgerclaw: room ${roomId} is encrypted, sending notice to trigger key rotation`);
-      await client.sendNotice(roomId, "🔐 Encryption active — session keys exchanged.");
-      logVerbose(`badgerclaw: sent encryption handshake notice in room ${roomId}`);
+      await client.sendNotice(
+        roomId,
+        "🔐 Connected — encryption active.\n\n" +
+          "I'll respond when @mentioned. To toggle auto-reply:\n" +
+          "• /bot talk on — I'll respond to every message\n" +
+          "• /bot talk off — I'll only respond when @mentioned\n" +
+          "• /bot help — see all commands",
+      );
+      logVerbose(`badgerclaw: sent encryption handshake + hint notice in room ${roomId}`);
     } catch (err) {
       runtime.log?.(`badgerclaw: encryption handshake failed for room ${roomId}: ${String(err)}`);
     }

package/src/onboarding.ts

@@ -245,15 +245,14 @@ export const badgerclawOnboardingAdapter: ChannelOnboardingAdapter = {
             autoJoin: "always",
             // Open policy: bot responds in any room it's invited to
             groupPolicy: "open",
-            // Default group config: auto-reply in all rooms with a helpful assistant prompt.
-            // This prevents the bot from inheriting workspace personas (SOUL.md) that may
-            // tell it to stay silent in groups or reply with NO_REPLY.
+            // Default group config: auto-reply in all rooms.
+            // No systemPrompt override — the bot respects the user's workspace personality
+            // (SOUL.md, IDENTITY.md, etc.). When the bot joins a group, it sends a hint
+            // message about /bot talk on|off so users know how to control it.
             groups: {
               "*": {
                 autoReply: true,
                 enabled: true,
-                systemPrompt:
-                  "You are a helpful AI assistant in a BadgerClaw encrypted chat room. Respond to messages directly and helpfully. Be concise and friendly.",
               },
             },
             dm: {