@toolpack-sdk/agents 2.3.0 → 2.5.0

package/dist/{index-BxUlu-qG.d.ts → index-BCBukKC4.d.ts}

@@ -1,4 +1,4 @@
-import { A as AgentInput, e as AgentOutput } from './types-C3eW-auY.js';
+import { A as AgentInput, f as AgentOutput } from './types-C3EZvpe0.js';
 import { Participant } from 'toolpack-sdk';
 
 /**
@@ -132,6 +132,15 @@ declare class SlackChannel extends BaseChannel {
      * ```
      */
     botUserId?: string;
+    /**
+     * The bot's Slack integration id (e.g. `'B_BOT123'`), populated by the
+     * startup self-check (`auth.test`) alongside `botUserId`.
+     *
+     * Used internally for self-suppression of DM `bot_message` events where
+     * Slack omits the `user` field (so `botUserId` comparison cannot fire).
+     * Not needed for regular channel posts — those carry `event.user`.
+     */
+    private botId?;
     /**
      * Normalized allowlist of channel identifiers, or `null` to accept any channel.
      * Derived from `config.channel` at construction time.
@@ -200,10 +209,11 @@ declare class SlackChannel extends BaseChannel {
      * 2. Channel allowlist (from `config.channel`): events outside the allowlist
      *    are dropped. DMs (`im`/`mpim`) always pass because they are per-user, not
      *    per-channel. Skipped entirely when `config.channel` is null/omitted.
-     * 3. **Self-suppression (automatic):** events where `event.user` matches this
-     *    channel's own `botUserId` are dropped. This prevents agents from looping
-     *    on their own posts and requires no configuration — `botUserId` is
-     *    discovered via `auth.test` at startup.
+     * 3. **Self-suppression (automatic):** events where `event.user` matches
+     *    `botUserId`, OR where `event.bot_id` matches `botId`, are dropped. This
+     *    handles both channel posts (where Slack sets `event.user`) and DM posts
+     *    (where Slack omits `event.user` but sets `event.bot_id`). Requires no
+     *    configuration — both ids are discovered via `auth.test` at startup.
      * 4. Events without `bot_id` (human messages) pass.
      * 5. Explicit blocklist check (`blockedBotIds`) runs first for bot messages.
      * 6. If `allowedBotIds` is provided, strict mode applies: only listed bots

package/dist/{index-DrigwC1A.d.cts → index-CA38tE7C.d.cts}

@@ -1,4 +1,4 @@
-import { A as AgentInput, e as AgentOutput } from './types-C3eW-auY.cjs';
+import { A as AgentInput, f as AgentOutput } from './types-C3EZvpe0.cjs';
 import { Participant } from 'toolpack-sdk';
 
 /**
@@ -132,6 +132,15 @@ declare class SlackChannel extends BaseChannel {
      * ```
      */
     botUserId?: string;
+    /**
+     * The bot's Slack integration id (e.g. `'B_BOT123'`), populated by the
+     * startup self-check (`auth.test`) alongside `botUserId`.
+     *
+     * Used internally for self-suppression of DM `bot_message` events where
+     * Slack omits the `user` field (so `botUserId` comparison cannot fire).
+     * Not needed for regular channel posts — those carry `event.user`.
+     */
+    private botId?;
     /**
      * Normalized allowlist of channel identifiers, or `null` to accept any channel.
      * Derived from `config.channel` at construction time.
@@ -200,10 +209,11 @@ declare class SlackChannel extends BaseChannel {
      * 2. Channel allowlist (from `config.channel`): events outside the allowlist
      *    are dropped. DMs (`im`/`mpim`) always pass because they are per-user, not
      *    per-channel. Skipped entirely when `config.channel` is null/omitted.
-     * 3. **Self-suppression (automatic):** events where `event.user` matches this
-     *    channel's own `botUserId` are dropped. This prevents agents from looping
-     *    on their own posts and requires no configuration — `botUserId` is
-     *    discovered via `auth.test` at startup.
+     * 3. **Self-suppression (automatic):** events where `event.user` matches
+     *    `botUserId`, OR where `event.bot_id` matches `botId`, are dropped. This
+     *    handles both channel posts (where Slack sets `event.user`) and DM posts
+     *    (where Slack omits `event.user` but sets `event.bot_id`). Requires no
+     *    configuration — both ids are discovered via `auth.test` at startup.
      * 4. Events without `bot_id` (human messages) pass.
      * 5. Explicit blocklist check (`blockedBotIds`) runs first for bot messages.
      * 6. If `allowedBotIds` is provided, strict mode applies: only listed bots