fix(discord): add agentComponents to config Zod schema by gambletan · Pull Request #39378 · openclaw/openclaw

gambletan · 2026-03-08T02:15:43Z

Summary

Adds agentComponents field to DiscordAccountSchema in the Zod config schema
Aligns schema with the TypeScript type definition DiscordAccountConfig at types.discord.ts:301

Problem

The agentComponents field is defined in the TypeScript type, actively read at runtime in discord/monitor/provider.ts:544-545, and used in tests — but was missing from the Zod validation schema. Because the schema uses .strict(), users setting channels.discord.agentComponents.enabled: true get an Unrecognized key validation error.

Fixes #35564

Test plan

Zod schema tests pass (12/12)
Setting channels.discord.agentComponents.enabled: true should be accepted

🤖 Generated with Claude Code

greptile-apps · 2026-03-08T02:18:13Z

Greptile Summary

This PR fixes a user-facing validation error by adding the missing agentComponents field to the DiscordAccountSchema Zod schema, aligning it with the existing DiscordAgentComponentsConfig TypeScript type and its active runtime usage in discord/monitor/provider.ts.

The new agentComponents sub-schema ({ enabled: z.boolean().optional() }.strict().optional()) exactly matches the DiscordAgentComponentsConfig type, which only exposes enabled?: boolean.
The placement in the schema (between execApprovals and ui) mirrors the ordering in the TypeScript interface, maintaining consistency and readability.
Without this change, any config containing channels.discord.agentComponents.enabled: true would be rejected at startup with an Unrecognized key error because the parent schema is .strict().
The schema uses .strict() and .optional() consistently with every other sub-object in the file.

Confidence Score: 5/5

This PR is safe to merge — it is a minimal, targeted schema fix with no logic changes.
The change is a single-field addition to a Zod schema that exactly mirrors the existing TypeScript type definition and the runtime code that already reads the field. There are no new behaviors introduced; the only effect is that previously-rejected valid config is now accepted. The schema uses .strict() and .optional() consistently with every other sub-object in the file. Runtime usage is confirmed in provider.ts where agentComponentsConfig is accessed and its enabled property controls whether agent-controlled interactive components are activated.
No files require special attention.

_{Last reviewed commit: 60ea20d}

@gambletan

…(thanks @gambletan)

thewilloftheshadow · 2026-03-08T03:12:17Z

Landed via temp rebase onto main.

Gate: related config tests only (bunx vitest run src/config/config.discord-agent-components.test.ts src/config/schema.test.ts src/config/schema.hints.test.ts)
Land commit: 2da9621
Source commit: 60ea20d
Merge commit: 9c8e34d

Thanks @gambletan!

@goodspeed-apps

* main: (290 commits) test: stabilize exec resolver timeout fixture chore: add changelog and format fix for openclaw#39414 fix(chat): preserve sender labels in dashboard history docs: clean up latest changelog sections docs: dedupe changelog contributor attribution fix(ci): resolve current gate regressions refactor(voice-call): share tts deep merge fix: land openclaw#39337 by @goodspeed-apps for acpx MCP bootstrap fix(ci): resolve type regressions on main fix: document discord agentComponents schema parity (openclaw#39378) (thanks @gambletan) (openclaw#39378) fix(discord): validate agentComponents config test: cover daemon probe auth seam refactor: preserve explicit mock voice-call values refactor: register gateway service adapters refactor: reuse shared gateway probe auth refactor: split daemon status gathering refactor: centralize strict numeric parsing refactor: normalize voice-call runtime defaults fix(ci): pin multi-arch docker base digests docs: add changelog for Telegram DM draft restore (openclaw#39398) ...

@gambletan