openclaw - 💡(How to fix) Fix Control UI shows wrong agent identity name for non-main agent sessions [1 comments, 2 participants]

Bug Description

When viewing a non-main agent session in the Control UI, the header displays the main agent's identity name instead of the correct agent name for that session.

Environment

• OpenClaw: 2026.4.24 (cbcfdf6)
• OS: macOS 26.4.1 (arm64)
• Node: v25.9.0

Setup

Multiple agents configured in openclaw.json:

{
  "agents": {
    "list": [
      {
        "id": "main",
        "name": "0.AI大管家(主)",
        "identity": { "name": "AI大管家", "emoji": "🤵" }
      },
      {
        "id": "fs-daying",
        "name": "1.大颖(主)",
        "identity": { "name": "大颖", "emoji": "💻" },
        "workspace": "/Users/rocky/.openclaw/workspace-fs-daying"
      }
    ]
  }
}

The fs-daying workspace also has an IDENTITY.md with Name: 大颖.

Expected Behavior

When viewing the agent:fs-daying:feishu:direct:* session in Control UI, the header should display "大颖".

Actual Behavior

Control UI header displays "AI大管家" (the main agent's name) regardless of which agent session is being viewed.

Investigation

1. resolveAssistantIdentity() in assistant-identity-B3FaldPp.js correctly resolves the name priority:

   • cfg.ui.assistant.name → not set
   • resolveAgentIdentity(cfg, agentId).name → "大颖" ✅
   • loadAgentIdentity(workspaceDir).name → "大颖" ✅
   • Default: "Assistant"

2. The agent.identity.get RPC handler calls resolveAssistantIdentity() with the correct agentId resolved from session key.

3. Session routing is correct — messages dispatch to agent:fs-daying properly.

4. Hard refresh (Cmd+Shift+R) does not fix the issue.

Hypothesis

Control UI may cache the main agent's identity on initial load and not re-fetch agent.identity.get when switching to a different agent's session. Or the call is not passing the correct sessionKey/agentId parameter.

Steps to Reproduce

1. Configure two agents with different identity.name values
2. Have a session for the non-main agent (e.g., via feishu channel)
3. Open Control UI
4. Switch to the non-main agent's session
5. Header shows main agent's name instead

Notes

• Config is verified correct — the gateway resolves the right identity
• Only the Control UI display is affected
• Actual agent behavior and routing work correctly