Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Discord progress commentary config is present in runtime but rejected by schema

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

OpenClaw 2026.5.28 appears to ship a partial Discord progress-commentary implementation: the installed runtime and UI hints know about channels.discord.streaming.progress.commentary, but openclaw config schema omits that field and openclaw config set ... --strict-json --dry-run rejects it.

This blocks users from enabling the opt-in Discord commentary progress feature added for #83307 / #85200 through the supported config CLI path.

Error Message

Error: Dry run failed: config schema validation failed.

    • channels.discord.streaming.progress: invalid config: must not have additional properties: "commentary"

Root Cause

Users trying to enable the new Discord commentary progress feature through the supported openclaw config CLI cannot do so on 2026.5.28, even though the release includes runtime pieces that suggest the feature should be available.

This makes the feature look broken or half-released and makes troubleshooting #88227 harder, because the first documented/configured knob for safe commentary progress cannot be enabled cleanly.

Code Example

node /app/openclaw.mjs config get channels.discord.streaming.mode

---

partial

---

node /app/openclaw.mjs config set channels.discord.streaming.mode progress --dry-run

---

Dry run note: value mode does not run schema/resolvability checks. Use --strict-json, builder flags, or batch mode to enable validation checks.
Dry run successful: 1 update(s) validated against ~/.openclaw/openclaw.json.

---

node /app/openclaw.mjs config set channels.discord.streaming.progress.commentary true --strict-json --dry-run

---

Error: Dry run failed: config schema validation failed.
- - channels.discord.streaming.progress: invalid config: must not have additional properties: "commentary"

---

node /app/openclaw.mjs config schema > /tmp/openclaw-schema.json
node -e "const s=require('/tmp/openclaw-schema.json'); const p=s.properties.channels.properties.discord.properties.streaming.properties.progress; console.log(JSON.stringify(p,null,2));"

---

{
  "type": "object",
  "properties": {
    "label": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "boolean",
          "const": false
        }
      ]
    },
    "labels": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "maxLines": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    },
    "maxLineChars": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    },
    "render": {
      "type": "string",
      "enum": [
        "text",
        "rich"
      ]
    },
    "toolProgress": {
      "type": "boolean"
    },
    "commandText": {
      "type": "string",
      "enum": [
        "raw",
        "status"
      ]
    }
  },
  "additionalProperties": false
}

---

grep -RIn --exclude-dir=node_modules "streaming.progress.commentary\\|Discord Progress Commentary\\|resolveChannelStreamingProgressCommentary\\|DiscordStreamingProgressSchema" /app/dist 2>/dev/null | head -80

---

/app/dist/bundled-channel-config-schema-B8zs_onv.js:120:const DiscordStreamingProgressSchema = ChannelStreamingProgressSchema.extend({ commentary: boolean().optional() }).strict();
/app/dist/bundled-channel-config-schema-B8zs_onv.js:130:const DiscordPreviewStreamingConfigSchema = ChannelPreviewStreamingConfigSchema.extend({ progress: DiscordStreamingProgressSchema.optional() }).strict();
/app/dist/config-schema-BeUb0EJF.js:95:  "streaming.progress.commentary": {
/app/dist/config-schema-BeUb0EJF.js:96:    label: "Discord Progress Commentary",
/app/dist/message-handler.process-CP-OZdtT.js:610: const commentaryProgressEnabled = Boolean(draftStream) && resolveChannelStreamingProgressCommentary(params.discordConfig);
/app/dist/streaming-Bv78t77e.js:412:function resolveChannelStreamingProgressCommentary(entry, defaultValue = false) {

---

{
  "channels": {
    "discord": {
      "streaming": {
        "mode": "progress",
        "progress": {
          "commentary": true,
          "toolProgress": false,
          "maxLines": 12,
          "label": false
        }
      }
    }
  }
}

---

channels.discord.streaming.progress: invalid config: must not have additional properties: "commentary"
RAW_BUFFERClick to expand / collapse

Summary

OpenClaw 2026.5.28 appears to ship a partial Discord progress-commentary implementation: the installed runtime and UI hints know about channels.discord.streaming.progress.commentary, but openclaw config schema omits that field and openclaw config set ... --strict-json --dry-run rejects it.

This blocks users from enabling the opt-in Discord commentary progress feature added for #83307 / #85200 through the supported config CLI path.

Environment

  • OpenClaw: OpenClaw 2026.5.28
  • Install/runtime path: Docker/containerized OpenClaw using /app/openclaw.mjs
  • Active config path reported by CLI: ~/.openclaw/openclaw.json
  • Channel: Discord

What I tried

Current Discord streaming mode:

node /app/openclaw.mjs config get channels.discord.streaming.mode

Output:

partial

progress mode itself can be dry-run set with value mode:

node /app/openclaw.mjs config set channels.discord.streaming.mode progress --dry-run

Output:

Dry run note: value mode does not run schema/resolvability checks. Use --strict-json, builder flags, or batch mode to enable validation checks.
Dry run successful: 1 update(s) validated against ~/.openclaw/openclaw.json.

But the new commentary option is rejected by the schema:

node /app/openclaw.mjs config set channels.discord.streaming.progress.commentary true --strict-json --dry-run

Output:

Error: Dry run failed: config schema validation failed.
- - channels.discord.streaming.progress: invalid config: must not have additional properties: "commentary"

Schema proof

The active CLI schema for channels.discord.streaming.progress does not include commentary:

node /app/openclaw.mjs config schema > /tmp/openclaw-schema.json
node -e "const s=require('/tmp/openclaw-schema.json'); const p=s.properties.channels.properties.discord.properties.streaming.properties.progress; console.log(JSON.stringify(p,null,2));"

Output:

{
  "type": "object",
  "properties": {
    "label": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "boolean",
          "const": false
        }
      ]
    },
    "labels": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "maxLines": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    },
    "maxLineChars": {
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 9007199254740991
    },
    "render": {
      "type": "string",
      "enum": [
        "text",
        "rich"
      ]
    },
    "toolProgress": {
      "type": "boolean"
    },
    "commandText": {
      "type": "string",
      "enum": [
        "raw",
        "status"
      ]
    }
  },
  "additionalProperties": false
}

Runtime/UI hint proof

The installed runtime appears to contain the commentary implementation and UI hint:

grep -RIn --exclude-dir=node_modules "streaming.progress.commentary\\|Discord Progress Commentary\\|resolveChannelStreamingProgressCommentary\\|DiscordStreamingProgressSchema" /app/dist 2>/dev/null | head -80

Relevant output:

/app/dist/bundled-channel-config-schema-B8zs_onv.js:120:const DiscordStreamingProgressSchema = ChannelStreamingProgressSchema.extend({ commentary: boolean().optional() }).strict();
/app/dist/bundled-channel-config-schema-B8zs_onv.js:130:const DiscordPreviewStreamingConfigSchema = ChannelPreviewStreamingConfigSchema.extend({ progress: DiscordStreamingProgressSchema.optional() }).strict();
/app/dist/config-schema-BeUb0EJF.js:95:  "streaming.progress.commentary": {
/app/dist/config-schema-BeUb0EJF.js:96:    label: "Discord Progress Commentary",
/app/dist/message-handler.process-CP-OZdtT.js:610: const commentaryProgressEnabled = Boolean(draftStream) && resolveChannelStreamingProgressCommentary(params.discordConfig);
/app/dist/streaming-Bv78t77e.js:412:function resolveChannelStreamingProgressCommentary(entry, defaultValue = false) {

So there are two conflicting signals in the same installed package:

  • Runtime/config-hint artifacts include streaming.progress.commentary.
  • openclaw config schema and validated config writes reject progress.commentary.

Expected behavior

The documented/proposed config from #83307 / #85200 should validate:

{
  "channels": {
    "discord": {
      "streaming": {
        "mode": "progress",
        "progress": {
          "commentary": true,
          "toolProgress": false,
          "maxLines": 12,
          "label": false
        }
      }
    }
  }
}

At minimum, the CLI schema, generated config metadata, runtime resolver, and docs should agree on whether channels.discord.streaming.progress.commentary is supported.

Actual behavior

progress.commentary is visible in installed runtime/UI hint artifacts, but the active CLI schema omits it and rejects the setting:

channels.discord.streaming.progress: invalid config: must not have additional properties: "commentary"

Related upstream context

  • #83307: Discord progress drafts should support assistant commentary events
  • #85200: Show assistant commentary in Discord progress drafts
  • #88227: Discord progress/partial streaming no longer shows visible in-progress updates
  • #87339: fix(discord): accumulate reasoning progress deltas

Why this matters

Users trying to enable the new Discord commentary progress feature through the supported openclaw config CLI cannot do so on 2026.5.28, even though the release includes runtime pieces that suggest the feature should be available.

This makes the feature look broken or half-released and makes troubleshooting #88227 harder, because the first documented/configured knob for safe commentary progress cannot be enabled cleanly.

Suggested fix

Regenerate or align the active config schema so channels.discord.streaming.progress.commentary is accepted when the Discord runtime supports it, and add/keep a schema regression test that verifies this exact path validates.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The documented/proposed config from #83307 / #85200 should validate:

{
  "channels": {
    "discord": {
      "streaming": {
        "mode": "progress",
        "progress": {
          "commentary": true,
          "toolProgress": false,
          "maxLines": 12,
          "label": false
        }
      }
    }
  }
}

At minimum, the CLI schema, generated config metadata, runtime resolver, and docs should agree on whether channels.discord.streaming.progress.commentary is supported.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Discord progress commentary config is present in runtime but rejected by schema