fix(telegram): allow agentId in account config for multi-account routing#2182
Open
BingqingLyu wants to merge 5 commits into
Open
fix(telegram): allow agentId in account config for multi-account routing#2182BingqingLyu wants to merge 5 commits into
BingqingLyu wants to merge 5 commits into
Conversation
Allows agentId in channels.telegram.accounts.<id> for per-account agent routing in multi-account setups. Fixes regression where upgrading from 2026.4.5 to 2026.4.8 caused 'must NOT have additional properties' errors for accounts with agentId configured.
Resolves Greptile P2 review comment: test was nested inside
telegram disableAudioPreflight schema block (semantically unrelated).
Now in dedicated describe("telegram account agentId schema") block.
…flight describe block
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.
Summary
Fixes regression where Telegram multi-account configs with
agentIdwere rejected as 'must NOT have additional properties' after upgrading from 2026.4.5 to 2026.4.8.Root cause
agentIdwas only defined inTelegramTopicSchema(for forum group topic routing), not inTelegramAccountSchemaBase. The.strict()Zod modifier generatesadditionalProperties: falsein JSON Schema, causing account configs withagentIdto fail validation.Changes
agentId?: stringtoTelegramAccountConfigtypeagentId: z.string().optional()toTelegramAccountSchemaBaseZod schema (afterenabledfield)agentIdin account configTesting
agentIdnow passes, multi-account config (6 accounts each withagentId) passes, backward compatibility preservedFixes openclaw#62985