fix(controller): avoid openclaw doctor migration on channel connect#736
Merged
fix(controller): avoid openclaw doctor migration on channel connect#736
Conversation
…enclaw doctor migration Channel config compiler was placing dmPolicy, allowFrom, groupPolicy at the channel top level while using named account IDs (not 'default'). OpenClaw doctor detected this as legacy single-account format and auto-migrated values into accounts.default, modifying the config file and triggering a second gateway restart on every new channel connect. Move these fields into each account object so doctor has nothing to migrate. Affects discord, slack, and feishu channels.
Siri-Ray
approved these changes
Apr 1, 2026
Merged
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
2 participants
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.
What
Move account-scoped channel config (
dmPolicy,allowFrom,groupPolicy) from channel top level into individual account objects.Why
When connecting a new channel (e.g. Discord), the config compiler placed
dmPolicy/allowFrom/groupPolicyat the channel top level (channels.discord.dmPolicy) while accounts used named IDs (e.g.discord-<APP_ID>). OpenClaw's doctor detected this as legacy single-account format and auto-migrated values intoaccounts.default, which:After the fix, connecting Discord triggers a single hot reload (
config hot reload applied) instead of two full gateway restarts.How
channel-binding-compiler.ts: MovedmPolicy,allowFrom,groupPolicyfrom channel top-level into each account object (discord, slack, feishu)openclaw-config.ts: AdddmPolicyandallowFromtodiscordAccountSchemaAffected areas
Checklist
pnpm typecheckpassespnpm lintpassespnpm testpassespnpm generate-typesrun (if API routes/schemas changed)anytypes introduced (useunknownwith narrowing)Notes for reviewers
Verified locally: Discord connect now shows
config hot reload applied (channels.discord)instead of doubleSIGUSR1 → gateway restart.