Repository navigation
Make the default OpenClaw agent display name configurable - #87
Open
JeffPengCoder wants to merge 1 commit into
Open
JeffPengCoder wants to merge 1 commit into
JeffPengCoder wants to merge 1 commit into
Conversation
Signed-off-by: Jeff Peng <jepeng@nvidia.com>
JeffPengCoder
requested review from
RohanAdwankar and
kgengedullay
as code owners
November 1, 2026 20:52
This was referenced Nov 1, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Allow deployments to give the default OpenClaw agent a recognizable display name without editing the seed JSON or changing its internal
defaultID. This applies to the agent across messaging channels; each channel controls how it presents the identity.Add optional
openclaw.agentDisplayName(empty by default). A nonempty string sets both the agentnameandidentity.name. Empty or unset values preserve the existingAI Factory Operations Agentname and absence of an explicit identity. Agent IDs, routing, session keys, and all other rendered OpenClaw configuration remain unchanged. The messaging platform’s bot/application profile name is managed separately.Includes installation/upgrade commands, type validation, JSON-safe string rendering, semantic render regression tests, and the regenerated agent documentation bundle. The change is based directly on upstream
mainand can be reviewed and merged independently of the Feishu channel PR.Validation:
node --test utils/*.test.mjs helm/mosaic-stack/tests/*.test.mjs tests/docs/*.test.mjs: 228 passed, 0 failed, 2 optional integration tests skipped (OpenClaw runtime memory and live VictoriaMetrics).node --test helm/afoa-inference/tests/*.test.mjs: 4 passed.helm lint helm/mosaic-stackandhelm lint helm/afoa-inference: passed.python3 docs/package_agent_docs.py --check: passed.sphinx-build -W --keep-going -q -b html -c docs . docs/_build/html: passed with no warnings.git diff --check: passed.The new tests compare the complete parsed config for default/empty/unset and overridden names, preserve the
defaultID, reject non-string values, and cover quotes, Unicode, backslashes, control characters, and Helm-looking text as literal data. The override is already in use on a Spark deployment with OpenClaw 2026.6.10; the source PR additionally preserves the upstream default behavior when no override is selected.