openclaw - 💡(How to fix) Fix Health check shows Feishu as OFF/not configured when using multi-account format [1 participants]

Bug Description

openclaw status --deep shows Feishu channel as OFF · not configured even when Feishu is fully configured and working (sending/receiving messages via WebSocket).

Environment

• OpenClaw: 2026.4.24
• OS: macOS 15.4 (arm64, M4 Pro)
• Node: v24.15.0
• Channel: Feishu (WebSocket mode)

Configuration Format

{
  "channels": {
    "feishu": {
      "enabled": true,
      "defaultAccount": "main-bot",
      "accounts": {
        "main-bot": {
          "appId": "cli_xxx",
          "appSecret": "...",
          "connectionMode": "websocket"
        },
        "marketing-agent": {
          "appId": "cli_yyy",
          "appSecret": "...",
          "connectionMode": "websocket"
        }
      }
    }
  }
}

Note: credentials are under accounts.*.appId/appSecret, NOT at channels.feishu.appId top-level.

Health Output

Health
┌─────────────────┬───────────┬────────────────────────┐
│ Item            │ Status    │ Detail                 │
├─────────────────┼───────────┼────────────────────────┤
│ Discord         │ OK        │ ok (@初号机:default)    │
│ Telegram        │ OK        │ ok (@FZMainBot:default) │
│ Feishu          │ OFF       │ not configured         │
│ openclaw-weixin │ OK        │ configured             │
└─────────────────┴───────────┴────────────────────────┘

Feishu is fully functional despite showing OFF.

Root Cause Analysis

I traced through the source code and identified the issue chain:

1. Gateway Health RPC (health-DpiT_nOq.js)

resolveHealthAccountContext() calls:

account = params.plugin.config.resolveAccount(params.cfg, params.accountId);

For Feishu, resolveAccount → resolveFeishuAccount → buildResolvedFeishuAccount which correctly merges account-level credentials via mergeFeishuAccountConfig() and sets configured: Boolean(baseCreds).

Then isConfigured(account) is called, which for Feishu is:

isConfigured: (account) => account.configured

This should return true since mergeFeishuAccountConfig correctly merges accounts["main-bot"].appId into the resolved account.

2. Status Lines (channel-BrSg_Wfu.js)

The resolveStatusLines function does:

const feishuCfg = cfg.channels?.feishu;
const resolvedCredentials = inspectFeishuCredentials(feishuCfg);

inspectFeishuCredentials only checks top-level feishuCfg.appId and feishuCfg.appSecret. When using multi-account format, these are undefined at the top level, so resolvedCredentials is null, and the probe never runs.

3. Health Formatting (health-format-Cu0AxhMs.js)

const configured = typeof baseSummary.configured === "boolean" ? baseSummary.configured : null;
if (configured === false) {
    lines.push(`${label}: not configured`);

If the Gateway returns configured: false for the Feishu channel, it displays "not configured".

Expected Behavior

Health check should correctly detect Feishu as configured when credentials are stored in the accounts sub-object format.

Possible Fix

1. In resolveStatusLines, use resolveFeishuAccount or iterate over accounts to find credentials instead of only checking top-level inspectFeishuCredentials(feishuCfg)
2. Ensure resolveHealthAccountContext properly resolves multi-account configurations

Workaround

This is a display-only bug. Feishu works correctly despite the health check showing OFF.