openclaw - 💡(How to fix) Fix [Feishu] WebChat UI displays sender user ID instead of friendly name despite resolveSenderNames being enabled [1 participants]

name: 🐞 Bug Report about: Create a report to help us improve title: "[Feishu] WebChat UI displays sender user ID instead of friendly name despite resolveSenderNames being enabled" labels: bug, feishu-channel, webchat

Bug Description

WebChat UI session list displays Feishu sender's user ID (e.g., ou_cab6e863739d5f3103f932ffdd09e15d) instead of the user's friendly name, even though resolveSenderNames: true is configured and Feishu app permissions are properly set up.

Steps to Reproduce

1. Configure Feishu channel in openclaw.json:

{
  channels: {
    feishu: {
      accounts: {
        august: {
          appId: "cli_xxx",
          appSecret: "xxx",
          name: "August",
          resolveSenderNames: true  // Explicitly enabled
        }
      }
    }
  }
}

1. Grant Feishu app permission contact:contact.base:readonly (读取用户基本信息)

2. Send a DM to the Feishu bot from a user account

3. Open WebChat UI (http://localhost:18789/)

4. Observe the session list - it shows the sender's user ID instead of their Feishu display name

Expected Behavior

WebChat UI should display the sender's Feishu display name (from their profile) in the session list, not their user ID.

Actual Behavior

Session list shows the raw Feishu user ID (e.g., ou_cab6e863739d5f3103f932ffdd09e15d) instead of the friendly name.

Investigation Findings

1. Permission is configured: contact:contact.base:readonly is granted in Feishu Open Platform
2. Config is correct: resolveSenderNames: true is set in openclaw.json
3. No permission errors in logs: August account doesn't show 99991672 permission errors
4. Session data shows user ID: The origin.label field in sessions.json contains the user ID, not the friendly name
5. No sender name resolution logs: Gateway logs don't show any resolveFeishuSenderName activity

Session data example:

{
  "origin": {
    "label": "ou_cab6e863739d5f3103f932ffdd09e15d",  // Should be friendly name
    "provider": "webchat",
    "surface": "webchat",
    "chatType": "direct",
    "from": "feishu:ou_cab6e863739d5f3103f932ffdd09e15d",
    "to": "user:ou_cab6e863739d5f3103f932ffdd09e15d",
    "accountId": "august"
  }
}

Root Cause Analysis

Based on code inspection of /opt/homebrew/lib/node_modules/openclaw/dist/monitor-Bkbv5nYZ.js:

1. The resolveFeishuSenderName() function exists and is called when resolveSenderNames: true
2. It calls Feishu API client.contact.user.get() to fetch user info
3. It extracts user?.name ?? user?.nickname ?? user?.en_name
4. However, the resolved senderName is not being persisted to the session's origin.label field
5. WebChat UI reads origin.label for display, which remains as the user ID

This appears to be a data flow bug where the resolved sender name is not correctly propagated to the session metadata that WebChat UI uses for display.

Environment

• OpenClaw Version: 2026.4.2
• Node.js: v23.11.0
• OS: Darwin 25.4.0 (arm64)
• Feishu Domain: feishu (China)
• Connection Mode: websocket

Additional Context

• Work account shows permission error 99991672 but August account does not
• The resolveSenderNames feature appears to be silently failing or not persisting results
• WebChat UI local alias feature works but is not persistent (stored in browser localStorage only)

Possible Fix

The senderName resolved by resolveFeishuSenderName() should be:

1. Logged for debugging purposes
2. Persisted to session metadata (origin.label or a dedicated displayName field)
3. Properly passed to WebChat UI session list rendering

Workarounds

Currently no effective workarounds:

• ❌ Modifying openclaw.json config (already tried)
• ❌ Setting Feishu app permissions (already configured)
• ❌ Modifying Feishu user profile name (doesn't help due to the bug)
• ⚠️ WebChat UI local alias (temporary, lost on browser cache clear)

Priority: Medium - affects user experience in multi-user deployments where session identification is important.