nextclaw 0.6.0 → 0.6.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +3 -3
  2. package/templates/USAGE.md +10 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "nextclaw",
3
- "version": "0.6.0",
3
+ "version": "0.6.1",
4
4
  "description": "Lightweight personal AI assistant with CLI, multi-provider routing, and channel integrations.",
5
5
  "private": false,
6
6
  "type": "module",
@@ -38,8 +38,8 @@
38
38
  "dependencies": {
39
39
  "chokidar": "^3.6.0",
40
40
  "commander": "^12.1.0",
41
- "@nextclaw/core": "^0.6.0",
42
- "@nextclaw/server": "^0.4.0"
41
+ "@nextclaw/core": "^0.6.1",
42
+ "@nextclaw/server": "^0.4.1"
43
43
  },
44
44
  "devDependencies": {
45
45
  "@types/node": "^20.17.6",
@@ -267,12 +267,15 @@ Configure channels in the UI at http://127.0.0.1:18791 or in `~/.nextclaw/config
267
267
  "discord": {
268
268
  "enabled": true,
269
269
  "token": "YOUR_BOT_TOKEN",
270
+ "allowBots": false,
270
271
  "allowFrom": []
271
272
  }
272
273
  }
273
274
  }
274
275
  ```
275
276
 
277
+ - `allowBots` (default `false`): whether to accept bot-authored messages. Keep it `false` unless you explicitly need bot-to-bot flows.
278
+
276
279
  ### Telegram
277
280
 
278
281
  1. Create a bot via [@BotFather](https://t.me/BotFather) and get the token.
@@ -293,6 +296,11 @@ Configure channels in the UI at http://127.0.0.1:18791 or in `~/.nextclaw/config
293
296
 
294
297
  Optional: set `"proxy": "http://localhost:7890"` (or your proxy URL) for network access.
295
298
 
299
+ Telegram Bot API behavior note:
300
+
301
+ - In **groups**, bots generally do **not** receive messages from other bots.
302
+ - For bot-to-bot scenarios, prefer **Telegram channels**. NextClaw now processes `channel_post` updates as inbound messages.
303
+
296
304
  ### Slack
297
305
 
298
306
  Socket mode is the typical setup. You need a **Bot Token** and an **App-Level Token** (with `connections:write`).
@@ -305,6 +313,7 @@ Socket mode is the typical setup. You need a **Bot Token** and an **App-Level To
305
313
  "mode": "socket",
306
314
  "botToken": "xoxb-...",
307
315
  "appToken": "xapp-...",
316
+ "allowBots": false,
308
317
  "dm": { "enabled": true, "allowFrom": [] }
309
318
  }
310
319
  }
@@ -313,6 +322,7 @@ Socket mode is the typical setup. You need a **Bot Token** and an **App-Level To
313
322
 
314
323
  - `dm.enabled`: allow DMs to the bot.
315
324
  - `dm.allowFrom`: restrict DMs to these user IDs; empty means allow all.
325
+ - `allowBots` (default `false`): whether bot-authored Slack messages can trigger replies.
316
326
 
317
327
  ### Feishu (Lark)
318
328