claude-slack-channel-bots 0.1.2 → 0.1.3

package/README.md

@@ -319,8 +319,11 @@ The `update-config` skill can automate hook installation. It copies or symlinks
 **routing.json CWD mismatch**
 If a Claude Code session connects but immediately disconnects, the session's actual CWD does not match any `cwd` in `routing.json`. Confirm the session's working directory matches the entry exactly (after tilde expansion). Duplicate CWDs across multiple routes are rejected at startup.
 
+**Bot not receiving messages in a new channel**
+After inviting the bot to a channel, Slack may not deliver messages until the bot is @mentioned for the first time. This is a Slack Socket Mode behavior — the first @mention activates event delivery for that channel. After that, all messages flow normally regardless of `requireMention` settings.
+
 **Channel not in access.json**
-Messages to channels not listed in `access.json → channels` are silently dropped. Use the `slack-channel-access` skill or edit `access.json` directly to add the channel ID with a `ChannelPolicy` entry.
+Messages to channels not listed in `access.json → channels` and not present in `routing.json → routes` are silently dropped. Use the `claude-slack-channels-config` skill or edit `access.json` directly to add the channel ID with a `ChannelPolicy` entry.
 
 **Permission relay not working**
 Check that the Slack app has interactivity enabled (Interactivity & Shortcuts → toggle on). Verify `curl` and `jq` are on your `PATH`. Confirm the hook scripts are executable (`chmod +x`). If the port was changed in `routing.json`, ensure `SLACK_STATE_DIR` is set correctly so the hooks can read the updated port.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-slack-channel-bots",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Multi-session Slack-to-Claude bridge — run multiple Claude Code bots across Slack channels via Socket Mode",
   "type": "module",
   "bin": {

package/skills/setup-slack-channel-bots/SKILL.md

@@ -174,7 +174,9 @@ After collecting at least one route, write the updated `routing.json`.
 **Important:** Remind the user to invite the bot to each channel they configured.
 In Slack, type `/invite @Claude Slack Channel Bots` in each channel (or whatever
 the bot's display name is). The bot cannot receive messages from channels it has
-not been invited to.
+not been invited to. After inviting, send an @mention to the bot in each channel
+— Slack may not deliver messages until the first @mention activates event
+delivery for that channel.
 
 **Optional routing fields** — after required routes are set, offer these with
 their defaults. Prompt only if the user wants to customise: