PR #70636: fix(ui): show agent display name for channel-prefixed session keys in switcher

• Repository: openclaw/openclaw
• Author: draix
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/70636

Description (problem / solution / changelog)

Problem

Closes #70610

Non-default agents accessed via channel plugins (e.g. webchat) appear in the session list under a legacy channel-prefixed key like webchat:g-agent-lottery-main instead of the canonical agent:lottery:main format. parseAgentSessionKey returns null for these keys, so the session switcher placed them in the "Other Sessions" group and used the raw key as the label:

Root Cause

In resolveSessionOptionGroups → addOption:

// Before — single parse attempt
const parsed = parseAgentSessionKey(key);
// null for webchat:g-agent-lottery-main → raw key used as label

Fix

Add tryParseChannelAgentKey(key, agents) that matches the {channel}:g-agent-{agentId}-{rest} pattern against the known agents list (sorted longest-first to avoid prefix collisions), returning a ParsedAgentSessionKey when a match is found.

addOption falls back to this function when parseAgentSessionKey returns null:

// After — fallback for channel-prefixed keys
const parsed =
  parseAgentSessionKey(key) ??
  tryParseChannelAgentKey(key, state.agentsList?.agents ?? []);

The original key is preserved as the option value so session switching continues to work. Only the display routing changes: the session is now placed in the correct agent group with the configured name (旺财 (lottery)) and the rest segment (main) as the option label.

Tests Added

resolveSessionOptionGroups — channel agent key fallback (#70610):

• routes webchat:g-agent-{id}-{rest} to the correct agent group
• leaves unmatched channel keys in Other Sessions (safe fallback)
• prefers canonical agent: key over fallback parsing (no regression)

Changed files

• ui/src/ui/app-render.helpers.node.test.ts (modified, +105/-0)
• ui/src/ui/app-render.helpers.ts (modified, +43/-2)