openclaw - ✅(Solved) Fix [Bug]: Feishu group chat: slash commands like /new, /status, and /model do not work and may lose message content [1 pull requests, 2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#49915Fetched 2026-04-08 01:01:18
View on GitHub
Comments
2
Participants
2
Timeline
18
Reactions
0
Author
Participants
Timeline (top)
referenced ×13commented ×2labeled ×2cross-referenced ×1

In a Feishu single-bot group chat with group-bound agent routing, slash commands such as /new, /status, and /model do not work. More importantly, they do not seem to reach the agent as normal text either. From the assistant side, these messages behave like empty-content events with metadata only. Environment Channel: Feishu Chat type: group chat Mode: single bot Routing: group-bound agent Feishu plugin: @larksuiteoapi/feishu-openclaw-plugin Plugin version: 2026.3.8

Root Cause

In a Feishu single-bot group chat with group-bound agent routing, slash commands such as /new, /status, and /model do not work. More importantly, they do not seem to reach the agent as normal text either. From the assistant side, these messages behave like empty-content events with metadata only. Environment Channel: Feishu Chat type: group chat Mode: single bot Routing: group-bound agent Feishu plugin: @larksuiteoapi/feishu-openclaw-plugin Plugin version: 2026.3.8

Fix Action

Fixed

PR fix notes

PR #49958: fix: allow commands in groups when no allowFrom is configured

Description (problem / solution / changelog)

Problem

Slash commands (/status, /new, /reset) silently fail in group chats when no allowFrom list is configured. The bot shows no response at all.

Root Cause

In resolveCommandAuthorizedFromAuthorizers (src/channels/command-gating.ts), when useAccessGroups is enabled (the default) and no allowFrom list exists, the authorizers array contains { configured: false, allowed: false }.

The code authorizers.some(e => e.configured && e.allowed) returns false because configured is false — meaning "no allowlist was set up". This incorrectly denies ALL commands in groups without an explicit allowFrom list.

The !useAccessGroups path already handles this correctly:

const anyConfigured = authorizers.some(e => e.configured);
if (!anyConfigured) return true; // No restrictions = allow

Fix

Added the same !anyConfigured guard to the useAccessGroups=true path. Both paths now treat "no restrictions configured" as "allow" consistently.

2 files changed, 26 insertions, 1 deletion.

Testing

  • command-gating.test.ts: 10/10 pass
  • Feishu bot test suite: 59/59 pass
  • No behavioral change for groups with allowFrom configured

Fixes #49915

Made-with: Claude Code

Changed files

  • src/channels/command-gating.test.ts (modified, +41/-1)
  • src/channels/command-gating.ts (modified, +6/-0)
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Summary

In a Feishu single-bot group chat with group-bound agent routing, slash commands such as /new, /status, and /model do not work. More importantly, they do not seem to reach the agent as normal text either. From the assistant side, these messages behave like empty-content events with metadata only. Environment Channel: Feishu Chat type: group chat Mode: single bot Routing: group-bound agent Feishu plugin: @larksuiteoapi/feishu-openclaw-plugin Plugin version: 2026.3.8

Steps to reproduce

  • Use OpenClaw in a Feishu group chat with a single bot and group-bound agent routing.
  • Send normal messages to establish context.
  • Send /new.
  • Ask a follow-up question that checks whether context was reset.
  • Send /status and /model or other slash commands.

Expected behavior

Either:

  • slash commands should work as OpenClaw control commands, or
  • at minimum, they should still be delivered to the agent as normal text

Actual behavior

/new does not reset the session/context /status and /model do not work slash messages do not appear to arrive as normal text from the assistant side, they look like empty-content events / metadata-only messages

OpenClaw version

<2026.3.13>

Operating system

ubuntu 22.04

Install method

npm

Model

gpt-5.4

Provider / routing chain

no sure

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

The fix involves updating the Feishu plugin to handle slash commands correctly. Here are the steps:

  • Update the @larksuiteoapi/feishu-openclaw-plugin to the latest version.
  • Modify the plugin configuration to include a custom message handler for slash commands.
  • Implement a custom handler to process slash commands and send them to the agent as normal text.

Example Code

// Import the required modules
const { FeishuPlugin } = require('@larksuiteoapi/feishu-openclaw-plugin');

// Create a new instance of the Feishu plugin
const feishuPlugin = new FeishuPlugin({
  // Plugin configuration
  appId: 'your_app_id',
  appSecret: 'your_app_secret',
});

// Define a custom message handler for slash commands
feishuPlugin.on('message', (message) => {
  if (message.text.startsWith('/')) {
    // Handle slash commands
    const command = message.text.substring(1);
    switch (command) {
      case 'new':
        // Reset the session/context
        break;
      case 'status':
        // Handle the status command
        break;
      case 'model':
        // Handle the model command
        break;
      default:
        // Handle unknown commands
        break;
    }
    // Send the command to the agent as normal text
    feishuPlugin.sendMessage(message.chatId, `/${command}`);
  }
});

Verification

To verify that the fix worked, send a slash command (e.g., /new) in the Feishu group chat and check if the command is executed correctly. Also, check if the command is delivered to the agent as normal text.

Extra Tips

  • Make sure to update the plugin to the latest version to ensure compatibility with the latest Feishu API changes.
  • Test the custom message handler thoroughly to ensure it handles all possible slash commands correctly.
  • Consider adding logging and error handling to the custom message handler to debug any issues that may arise.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Either:

  • slash commands should work as OpenClaw control commands, or
  • at minimum, they should still be delivered to the agent as normal text

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING