The "explicit" session type (used for portal/webchat and named session bindings) is silently dropped. Users who add "explicit" to allowedChatTypes in their config see no error, but active memory never runs in those sessions. 2. An error/warning is surfaced when an unrecognized chat type is configured

TL;DR

Update the normalizePluginConfig function to either include "explicit" in the allowedChatTypes whitelist or replace the whitelist with a more permissive validation that warns on unknown values.

Guidance

• Extend the existing filter to include "explicit": raw.allowedChatTypes.filter((value) => ["direct", "group", "channel", "explicit"].includes(value))
• Replace the whitelist with a more permissive validation that warns on unknown values, such as using a Set to check for known values and logging a warning for unknown values
• Consider adding input validation to the allowedChatTypes configuration to prevent unrecognized chat types from being set
• Review the requirements for active memory in explicit sessions to ensure the updated implementation meets the necessary functionality

Example

const knownChatTypes = new Set(["direct", "group", "channel", "explicit"]);
raw.allowedChatTypes = raw.allowedChatTypes.filter((value) => {
  if (!knownChatTypes.has(value)) {
    console.warn(`Unrecognized chat type: ${value}`);
  }
  return knownChatTypes.has(value);
});

Notes

The updated implementation should be tested to ensure it correctly handles the "explicit" session type and provides the expected functionality for users with webchat/portal sessions.

Recommendation

Apply workaround: Update the normalizePluginConfig function to include "explicit" in the allowedChatTypes whitelist or replace the whitelist with a more permissive validation, as this will provide the necessary functionality for users with webchat/portal sessions.