Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Allow custom agent name display in webchat control UI [1 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#49382•Fetched 2026-04-08 00:55:42
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
liudashu-cdliudashu-cd
Participants
liudashu-cdliudashu-cd
Timeline (top)
labeled ×1

The webchat control UI currently displays a hardcoded "assistant" label instead of the configured agent name (e.g., "小红 🌸") defined in openclaw.json under agents.list[].name. This feature request asks for dynamic display of the configured agent name or a custom label configuration option in webchat.

Root Cause

The webchat control UI currently displays a hardcoded "assistant" label instead of the configured agent name (e.g., "小红 🌸") defined in openclaw.json under agents.list[].name. This feature request asks for dynamic display of the configured agent name or a custom label configuration option in webchat.

RAW_BUFFERClick to expand / collapse

Summary

The webchat control UI currently displays a hardcoded "assistant" label instead of the configured agent name (e.g., "小红 🌸") defined in openclaw.json under agents.list[].name. This feature request asks for dynamic display of the configured agent name or a custom label configuration option in webchat.

Problem to solve

Users who configure custom agent names (like "小红 🌸") in their openclaw.json configuration expect to see this personalized name displayed in the webchat interface. Currently, regardless of what name is set in the config, the webchat control UI always shows the generic "assistant" label. This breaks the user experience for those who want a personalized chat assistant with a custom identity and makes it confusing when managing multiple agents or demonstrating the system to others.

Proposed solution

Option 1 (Recommended): Modify the webchat plugin to read and display the configured agent name from agents.list[].name dynamically instead of using a hardcoded "assistant" label.

Option 2: Add a new configuration option webchat.sessionLabel that allows users to customize the display name shown in the webchat interface independently.

Technical Implementation:

  • In Option 1, update the webchat plugin to fetch the agent name from the OpenClaw config during session initialization.
  • In Option 2, extend the config schema with a new field and use it for rendering the label in the UI.

Both options should maintain backward compatibility by defaulting to "assistant" if no custom name is configured.

Alternatives considered

No response

Impact

Affected Users: All users who have configured custom agent names in openclaw.json and use webchat as their primary interface.

Severity: Low-Medium (cosmetic issue, but affects user experience)

Frequency: Always occurs when using webchat with a custom agent name.

Consequence:

  • Reduced personalization and professionalism of the chat assistant
  • Confusion for new users who don't understand why their configured name isn't showing
  • Inconsistent branding when demonstrating OpenClaw to others or in production environments
  • Minor but noticeable UX friction for users expecting a customized experience

Evidence/examples

No response

Additional information

No response

extent analysis

Fix Plan

To address the issue, we will implement Option 1: Dynamic Agent Name Display. Here are the steps:

  • Update the webchat plugin to read the agents.list[].name from openclaw.json during session initialization.
  • Modify the UI rendering code to display the fetched agent name instead of the hardcoded "assistant" label.

Example code snippet (assuming a JavaScript-based webchat plugin):

// Fetch agent name from openclaw.json during session initialization
const agentName = getAgentNameFromConfig();

// Render the agent name in the UI
const labelElement = document.getElementById('agent-label');
labelElement.textContent = agentName;

// Helper function to fetch agent name from config
function getAgentNameFromConfig() {
  const config = getConfig(); // Assume a function to fetch openclaw.json config
  const agents = config.agents.list;
  const agentName = agents[0].name; // Assume the first agent is the default
  return agentName || 'assistant'; // Default to "assistant" if no name is configured
}

Verification

To verify the fix, follow these steps:

  • Configure a custom agent name in openclaw.json (e.g., "小红 🌸").
  • Restart the webchat session.
  • Verify that the custom agent name is displayed in the webchat interface instead of the hardcoded "assistant" label.

Extra Tips

  • Ensure that the getAgentNameFromConfig function is robust and handles cases where the config file is missing or malformed.
  • Consider adding a fallback mechanism to display a default label if the agent name is not configured or cannot be fetched.
  • Test the fix with different custom agent names and configurations to ensure backward compatibility and correct rendering.

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…
#api#ssr#installation#tensor shape#autograd error#container setup#orchestration issue#cache issue#memory leak#API versioning

Still need to ship something?

×6

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

Back to top recommendations

TRENDING