Summary
When running multiple OpenClaw instances, all browser tabs show the same hardcoded title "OpenClaw Control", making it difficult to distinguish between them.
Problem to solve
When running multiple OpenClaw instances, all browser tabs show the same hardcoded title "OpenClaw Control", making it difficult to distinguish between them.
Proposed solution
Add a gateway.controlUi.title config option that sets the HTML <title> of the Control UI. The gateway could inject it at serve-time or the UI could fetch it via the WebSocket.
{
gateway: {
controlUi: {
title: "Rainmaker 🌧️"
}
}
}
When unset, fall back to the current default ("OpenClaw Control").
Alternatives considered
Manually editing dist/control-ui/index.html, which gets overwritten on updates.
Impact
Affected: users
Severity: annoying
Frequency: Always
Consequence: ?? If you're on the wrong claw, who knows what may happen given
Evidence/examples
No response
Additional information
No response
Summary
When running multiple OpenClaw instances, all browser tabs show the same hardcoded title "OpenClaw Control", making it difficult to distinguish between them.
Problem to solve
When running multiple OpenClaw instances, all browser tabs show the same hardcoded title "OpenClaw Control", making it difficult to distinguish between them.
Proposed solution
Add a
gateway.controlUi.titleconfig option that sets the HTML<title>of the Control UI. The gateway could inject it at serve-time or the UI could fetch it via the WebSocket.When unset, fall back to the current default ("OpenClaw Control").
Alternatives considered
Manually editing
dist/control-ui/index.html, which gets overwritten on updates.Impact
Affected: users
Severity: annoying
Frequency: Always
Consequence: ?? If you're on the wrong claw, who knows what may happen given
Evidence/examples
No response
Additional information
No response