Bug type

Behavior bug

Summary

In OpenClaw 2026.3.24, the bundled Microsoft Teams runtime reads channels.msteams.feedbackEnabled and related keys, but config validation rejects those same keys as unrecognized.

Steps to reproduce

1. Install/run OpenClaw 2026.3.24.
2. Add channels.msteams.feedbackEnabled: false to ~/.openclaw/openclaw.json.
3. Run OpenClaw or trigger config validation/reload.
4. Observe config validation errors for channels.msteams.feedbackEnabled.
5. Inspect the installed bundled Teams runtime and observe that it reads channels?.msteams?.feedbackEnabled and related keys.

Expected behavior

If the bundled Teams runtime supports channels.msteams.feedbackEnabled and related keys, config validation should accept those keys.

Actual behavior

Config validation rejects the key with:
channels.msteams: Unrecognized key: "feedbackEnabled"

At the same time, the bundled 2026.3.24 Teams runtime contains code paths that read:

• channels?.msteams?.feedbackEnabled
• channels?.msteams?.feedbackReflection
• channels?.msteams?.feedbackReflectionCooldownMs
• channels?.msteams?.welcomeCard
• channels?.msteams?.groupWelcomeCard
• channels?.msteams?.promptStarters

OpenClaw version

2026.3.24

Operating system

macOS 26.3

Install method

pnpm global

Model

NOT_ENOUGH_INFO

Provider / routing chain

NOT_ENOUGH_INFO

Additional provider/model setup details

NOT_ENOUGH_INFO

Logs, screenshots, and evidence

Observed config validation error:

Invalid config at /Users/gumclaw/.openclaw/openclaw.json:
- channels.msteams: Unrecognized key: "feedbackEnabled"

Observed in installed bundled runtime (2026.3.24):

src-Ba9lUiIw.js:1259: const feedbackLoopEnabled = params.cfg.channels?.msteams?.feedbackEnabled !== false;
src-Ba9lUiIw.js:2117: if (msteamsCfg?.feedbackEnabled === false) {
src-Ba9lUiIw.js:2187: if (isNegative && msteamsCfg?.feedbackReflection !== false) ...
src-Ba9lUiIw.js:2246: if (isPersonal && msteamsCfg?.welcomeCard !== false) {
src-Ba9lUiIw.js:2249: promptStarters: msteamsCfg?.promptStarters
src-Ba9lUiIw.js:2263: } else if (!isPersonal && msteamsCfg?.groupWelcomeCard === true) {
src-Ba9lUiIw.js:388: const cooldownMs = cfg.channels?.msteams?.feedbackReflectionCooldownMs ?? 3e5;

Impact and severity

Affected users/systems/channels: Microsoft Teams setups on 2026.3.24 using the bundled Teams extension
Severity: Medium
Frequency: Reproduced when adding the key to config
Consequence: Operators cannot configure documented/runtime-supported Teams UX toggles through config because validation rejects them

Additional information

This report is about the config/schema mismatch only.

Grounded evidence shows the runtime reads these keys while validation rejects them. I did not verify whether these keys are documented publicly yet, only that they are implemented in the bundled runtime and rejected by config validation.