Skip to content

GHCR 2026.5.28 image emits stale Discord progress commentary config schema #88788

Closed as not planned

Description

@ericpearson

Summary

The running GHCR/Docker OpenClaw artifact for 2026.5.28 emits a CLI config schema that rejects channels.discord.streaming.progress.commentary, even though the source/tag and some installed runtime files indicate that Discord progress commentary support should be present.

This is a packaging/generated-artifact report, not a request to re-implement #85200.

The previous source-level issue was closed as already implemented: #88779. ClawSweeper specifically suggested treating any remaining container-only mismatch as a fresh packaging report with image evidence, so this issue focuses on the running container artifact.

Environment

  • Deployment source: GHCR OpenClaw Docker image (ghcr.io/openclaw/...)
  • Runtime path: containerized OpenClaw, /app/openclaw.mjs
  • Running container hostname: 8f713a0550a4
  • Running Docker container id from cgroup: 8f713a0550a46406bb9be63d98a3d112de55365dbe8c7815634280de5431a610
  • Docker socket: not mounted in this container
  • Portainer API key: not available inside this container
  • GHCR manifest/digest lookup from inside the container: unauthenticated registry requests returned 401

Because there is no Docker socket and no Portainer API key inside the container, I cannot include the image digest from this runtime. But the container was pulled from GHCR and the package/runtime version below is from inside that running container.

Running version proof

node /app/openclaw.mjs --version
node -e "const p=require('/app/package.json'); console.log(JSON.stringify({packageName:p.name,packageVersion:p.version},null,2))"
hostname
cat /proc/self/cgroup | head -20

Output:

OpenClaw 2026.5.28
{
  "packageName": "openclaw",
  "packageVersion": "2026.5.28"
}
8f713a0550a4
9:blkio:/docker/8f713a0550a46406bb9be63d98a3d112de55365dbe8c7815634280de5431a610
8:devices:/docker/8f713a0550a46406bb9be63d98a3d112de55365dbe8c7815634280de5431a610
7:freezer:/docker/8f713a0550a46406bb9be63d98a3d112de55365dbe8c7815634280de5431a610
6:memory:/docker/8f713a0550a46406bb9be63d98a3d112de55365dbe8c7815634280de5431a610
5:cpu:/docker/8f713a0550a46406bb9be63d98a3d112de55365dbe8c7815634280de5431a610
4:cpuset:/docker/8f713a0550a46406bb9be63d98a3d112de55365dbe8c7815634280de5431a610
3:cpuacct:/docker/8f713a0550a46406bb9be63d98a3d112de55365dbe8c7815634280de5431a610
2:name=synomonitor:/system.slice/pkg-ContainerManager-dockerd.service
1:name=systemd:/docker/8f713a0550a46406bb9be63d98a3d112de55365dbe8c7815634280de5431a610

Reproduction

Inside that running container:

node /app/openclaw.mjs config schema > /tmp/openclaw-schema-current.json
node -e "const s=require('/tmp/openclaw-schema-current.json'); const props=s.properties.channels.properties.discord.properties.streaming.properties.progress.properties; console.log('hasCommentary=' + Object.prototype.hasOwnProperty.call(props,'commentary')); console.log(Object.keys(props).sort().join(','));"

Output:

hasCommentary=false
commandText,label,labels,maxLineChars,maxLines,render,toolProgress

Attempting to validate the documented/implemented setting fails:

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"

Why this looks like an artifact mismatch

The same installed /app/dist tree contains runtime/UI-hint references to the field:

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

Relevant output from the same running container:

/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 the running artifact appears internally inconsistent:

  • Runtime/UI-hint files include streaming.progress.commentary.
  • The CLI schema emitted by node /app/openclaw.mjs config schema omits commentary.
  • Strict validated config writes reject the field.

Expected behavior

For a 2026.5.28 GHCR image that includes the #85200 runtime/docs/schema work, this should validate:

{
  "channels": {
    "discord": {
      "streaming": {
        "mode": "progress",
        "progress": {
          "commentary": true
        }
      }
    }
  }
}

At minimum, the generated CLI schema in the shipped Docker image should agree with the runtime resolver and UI hints in the same image.

Actual behavior

The GHCR-pulled running container reports OpenClaw 2026.5.28 / openclaw@2026.5.28, but its live CLI schema rejects channels.discord.streaming.progress.commentary.

Related context

Suggested investigation

Please check whether the GHCR Docker image published for 2026.5.28 includes a stale generated root config schema or mixed generated artifacts. A useful regression would be an image/package-level smoke test that runs:

node /app/openclaw.mjs config schema

and asserts that channels.discord.streaming.progress.properties.commentary exists when the Discord runtime bundle includes resolveChannelStreamingProgressCommentary.

Activity

  1. clawsweeper commented on May 31, 2026

    @clawsweeper
    Contributor

    Thanks for the report. I gave this a fresh shell check against current main, and I could not reproduce it anymore.

    Close: the exact GHCR 2026.5.28 Docker path now emits and validates the Discord progress commentary config key, and the current latest/2026.6.8 image passes the same checks.

    Review details

    Best possible solution:

    Keep the current GHCR/source behavior; if a future container shows this again, open a new digest-specific artifact report with fresh schema and strict dry-run output.

    Do we have a high-confidence way to reproduce the issue?

    No. The exact current GHCR 2026.5.28 amd64 image now emits the commentary schema property and accepts the strict dry-run config write, so the reported failure did not reproduce.

    Is this the best way to solve the issue?

    Yes. Closing as no longer reproducible is the narrowest current outcome because both the historical tag and the latest image pass the reported schema/config checks.

    Security review:

    Security review: No patch is under review, so there is no diff-level security review to perform.

    AGENTS.md: found and applied where relevant.

    What I checked:

    • Current GHCR 2026.5.28 schema smoke: Running ghcr.io/openclaw/openclaw:2026.5.28 now prints OpenClaw 2026.5.28, hasCommentary=true, and progress keys including commentary.
    • Current GHCR 2026.5.28 strict config dry-run: The reported strict config write now succeeds in the 2026.5.28 image: Dry run successful: 1 update(s) validated against $OPENCLAW_HOME/.openclaw/openclaw.json..
    • Registry digest matches the reported artifact: The current 2026.5.28 tag resolves to index digest sha256:dbad4655fb87aa8d8662323daf9f46f4721504324e22c9f99d84849e609f5b2c, and the linux/amd64 child is sha256:4e23676146b60da884d4a6ee050086cad7478c6041853f56eab9db0aad002921, matching the reporter's digest evidence.
    • Current latest release image also passes: latest resolves to OpenClaw 2026.6.8 and also emits hasCommentary=true and accepts the strict dry-run config write.
    • Current source schema includes the key: Current main includes commentary: z.boolean().optional() in the shared channel progress streaming schema. (src/config/zod-schema.providers-core.ts:102, a1271830948b)
    • Current schema test covers generated root schema: Current tests assert that generated root channel schemas expose commentary for Discord, Slack, and Telegram progress streaming. (src/config/schema.test.ts:305, a1271830948b)

    Likely related people:

    • bryanpearson: The merged Discord commentary feature credits this person as co-author and the original linked feature request author for the config/runtime surface. (role: feature originator and co-author; confidence: high; commits: ae30b4987ebe, 4df1fcf7b392; files: src/config/zod-schema.providers-core.ts, src/config/schema.test.ts, extensions/discord/src/config-ui-hints.ts)
    • steipete: GitHub PR metadata shows this person merged the implementation PR and authored follow-up fixup commits plus the v2026.5.28 release-adjacent commit inspected here. (role: merger and release-adjacent contributor; confidence: medium; commits: c8c99ac58a5d, 517450265a74, f7158a4fda32; files: extensions/discord/src/monitor/message-handler.draft-preview.ts, extensions/discord/src/monitor/message-handler.process.ts, .github/workflows/docker-release.yml)
    • vincentkoc: Current checkout blame/log on the central schema and Docker release workflow points to recent current-main commits by this person, so they are a likely routing candidate for follow-up release-smoke work. (role: recent current-main and release workflow contributor; confidence: medium; commits: a1271830948b, 4f278ef71c6f; files: src/config/zod-schema.providers-core.ts, .github/workflows/docker-release.yml, scripts/release-preflight.mjs)

    Codex review notes: model internal, reasoning high; reviewed against a1271830948b.

  2. added
    P2Normal backlog priority with limited blast radius.
    impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.
    issue-rating: 🦐 gold shrimpDecent issue quality, but reproduction details are still incomplete.
    clawsweeper:needs-infoClawSweeper needs more reporter information before it can verify this issue.
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.
    on May 31, 2026
  3. ericpearson commented on May 31, 2026

    @ericpearson
    Author

    Additional local remediation attempt and deployment check:

    I ran openclaw doctor --fix inside the affected container before retrying the schema path.

    Doctor did make unrelated config/state repairs:

    Moved messages.tts.providers.elevenlabs.voiceId → messages.tts.providers.elevenlabs.speakerVoiceId.
    Plugin registry refreshed: 7/95 enabled plugins indexed.
    Tightened permissions on ~/.openclaw to 700
    Repaired Codex session routes: moved 22 sessions across 1 store to openai/* while preserving auth-profile pins.
    

    It then exited nonzero while trying to install shell completion:

    Error: Failed to install completion: EACCES: permission denied, open '/home/node/.bashrc'
    

    After doctor, the schema mismatch still reproduced:

    node /app/openclaw.mjs config schema > /tmp/openclaw-schema-after-doctor.json
    node -e "const s=require('/tmp/openclaw-schema-after-doctor.json'); const props=s.properties.channels.properties.discord.properties.streaming.properties.progress.properties; console.log('hasCommentary=' + Object.hasOwn(props,'commentary')); console.log(Object.keys(props).sort().join(','));"

    Output:

    hasCommentary=false
    commandText,label,labels,maxLineChars,maxLines,render,toolProgress
    

    And the validated config write still failed:

    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"
    

    Since doctor did not fix it, I triggered the Docker updater webhook flow from this deployment. The update worker run id is:

    5f41f019-fdff-4334-ac51-369eac2d78e9
    

    The worker is configured to redeploy via the existing updater webhook, then perform a delayed post-restart check of:

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

    If the fresh pull/redeploy still reproduces the same failure, that should prove this is reproducible from the current GHCR Docker artifact rather than local config drift. The next useful validation from maintainers would be to pull the same GHCR image into a clean container, configure Discord, set channels.discord.streaming.mode=progress plus streaming.progress.commentary=true, and verify with an actual Discord turn that the progress draft shows commentary before final delivery.

  4. ericpearson commented on May 31, 2026

    @ericpearson
    Author

    @clawsweeper re-review

    Please review this fresh packaging-specific report. This is intentionally scoped to the running GHCR/Docker artifact, not to the already-merged source implementation in #85200.

    Since filing, I also ran openclaw doctor --fix; it made unrelated repairs but the same schema failure still reproduces:

    hasCommentary=false
    commandText,label,labels,maxLineChars,maxLines,render,toolProgress
    

    and:

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

    I then triggered the deployment updater webhook so the current deployment pulls/redeploys. If the post-redeploy check still shows hasCommentary=false, that should be strong evidence this is reproducible from the current GHCR artifact rather than local config drift.

    The requested maintainer validation is: pull the relevant GHCR image, run node /app/openclaw.mjs config schema, confirm whether channels.discord.streaming.progress.properties.commentary exists, then try a Discord config/run with streaming.mode=progress and streaming.progress.commentary=true.

  5. clawsweeper commented on May 31, 2026

    @clawsweeper
    Contributor

    🦞🧹
    ClawSweeper re-review requested.

    I asked ClawSweeper to review this item again.
    Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
    Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

    Re-review progress:

  6. ericpearson commented on May 31, 2026

    @ericpearson
    Author

    Post-redeploy verification from the affected deployment:

    The Docker updater webhook completed successfully from this deployment:

    Stack redeployed (HTTP 200)
    === Update complete ===
    

    I then rechecked the live container after the delayed post-restart window.

    Timestamp:

    2026-05-31 23:01:19 UTC
    

    Running version and package:

    OpenClaw 2026.5.28
    openclaw@2026.5.28
    

    The emitted runtime config schema still does not include the Discord progress commentary key:

    node - <<'NODE'
    const {execFileSync}=require('child_process');
    const schema=JSON.parse(execFileSync('node',['/app/openclaw.mjs','config','schema'],{
      encoding:'utf8',
      maxBuffer: 20 * 1024 * 1024,
    }));
    const p=schema.properties?.channels?.properties?.discord?.properties?.streaming?.properties?.progress;
    console.log('hasCommentary=' + Boolean(p?.properties?.commentary));
    console.log('progressKeys=' + Object.keys(p?.properties || {}).sort().join(','));
    NODE

    Output:

    hasCommentary=false
    progressKeys=commandText,label,labels,maxLineChars,maxLines,render,toolProgress
    

    The strict config write still fails after redeploy:

    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"
    

    So the remediation chain is now:

    1. openclaw doctor --fix was run and made unrelated repairs, but did not fix the schema.
    2. The Docker updater webhook redeployed the stack successfully.
    3. The live container still reports OpenClaw 2026.5.28.
    4. The live emitted schema still lacks channels.discord.streaming.progress.commentary.
    5. The live strict config path still rejects the documented key.

    This continues to look like the currently deployed GHCR image/package artifact is stale or mixed for the generated runtime schema, even though source/tag contain the feature.

  7. ericpearson commented on May 31, 2026

    @ericpearson
    Author

    @clawsweeper re-review

    Please re-review with the new post-redeploy evidence now attached in #88788 (comment).

    The affected deployment has now gone through the full local remediation chain:

    1. openclaw doctor --fix ran and made unrelated repairs.
    2. The Docker updater webhook completed successfully with:
    Stack redeployed (HTTP 200)
    === Update complete ===
    
    1. After the delayed post-restart window, the live container still reports:
    OpenClaw 2026.5.28
    openclaw@2026.5.28
    hasCommentary=false
    progressKeys=commandText,label,labels,maxLineChars,maxLines,render,toolProgress
    
    1. The strict config write still fails:
    channels.discord.streaming.progress: invalid config: must not have additional properties: "commentary"
    

    This should move the issue from "possible local config drift" to "reproducible after a successful redeploy from the current deployed GHCR/container path." Please re-check whether maintainers need to pull/inspect the published GHCR image/manifest, not just source or the v2026.5.28 tag.

  8. clawsweeper commented on May 31, 2026

    @clawsweeper
    Contributor

    🦞👀
    ClawSweeper picked this up.

    Command router queued. I will update this comment with the next step.

    Re-review progress:

  9. ericpearson commented on May 31, 2026

    @ericpearson
    Author

    @clawsweeper re-review

    One important clarification about the deployment/update path, since this issue is specifically about the published container artifact:

    This deployment is not rebuilding OpenClaw from local source and it is not using an in-container git checkout. The container reports the normal Docker behavior for gateway update.run as not-git-install, so updates are handled by an external updater webhook:

    POST http://192.168.1.185:9800/hooks/update-openclaw
    Body: {"version":"latest"}
    

    That webhook runs outside the OpenClaw app container and redeploys the stack. In this run it completed with:

    Stack redeployed (HTTP 200)
    === Update complete ===
    

    After that external redeploy/pull path, the restarted app container still reported:

    OpenClaw 2026.5.28
    openclaw@2026.5.28
    hasCommentary=false
    progressKeys=commandText,label,labels,maxLineChars,maxLines,render,toolProgress
    

    and still rejected:

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

    So the SHA/version/runtime evidence here should be treated as coming from the deployed GHCR Docker artifact selected by the updater, not from a local source checkout. The missing remaining evidence is the exact GHCR image digest/manifest from the host or registry side; the affected app container does not have Docker socket access, so it can verify runtime contents but cannot inspect its own pulled image digest.

    Please re-review with that in mind: the requested maintainer repro is to pull/inspect the published GHCR image/manifest selected for latest/2026.5.28, then run the container's own node /app/openclaw.mjs config schema smoke and confirm whether the emitted schema includes channels.discord.streaming.progress.properties.commentary.

  10. clawsweeper commented on May 31, 2026

    @clawsweeper
    Contributor

    🦞👀
    ClawSweeper picked this up.

    Command router queued. I will update this comment with the next step.

    Re-review progress:

  11. 14 remaining items

  12. added
    clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.
    issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.
    clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.
    impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.
    and removed
    clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.
    clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.
    issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.
    clawsweeper:needs-infoClawSweeper needs more reporter information before it can verify this issue.
    issue-rating: 🦐 gold shrimpDecent issue quality, but reproduction details are still incomplete.
    on Jun 2, 2026
  13. added
    clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.
    and removed
    clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.
    on Jun 19, 2026
  14. locked as resolved and limited conversation to collaborators on Jun 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions