openclaw - 💡(How to fix) Fix [Bug]: 2026.4.5 accepts agents.defaults.videoGenerationModel in config validate but flags it as unrecognized in memory/tasks commands [1 participants]

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…
GitHub stats
openclaw/openclaw#61989Fetched 2026-04-08 03:10:28
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0

In the installed OpenClaw 2026.4.5 CLI on macOS 26.3.1, openclaw config validate accepts a config containing agents.defaults.videoGenerationModel, but openclaw memory status and openclaw tasks list report the same key as unrecognized.

Root Cause

In the installed OpenClaw 2026.4.5 CLI on macOS 26.3.1, openclaw config validate accepts a config containing agents.defaults.videoGenerationModel, but openclaw memory status and openclaw tasks list report the same key as unrecognized.

Code Example

Invalid config at ~/.openclaw/openclaw.json:\n- agents.defaults: Unrecognized key: "videoGenerationModel"

---

"agents": {
  "defaults": {
    "videoGenerationModel": {
      "primary": "xai-images/grok-imagine-video"
    }
  }
}

---

$ /opt/homebrew/bin/openclaw --version
OpenClaw 2026.4.5 (3e72c03)

$ openclaw config validate
Config valid: ~/.openclaw/openclaw.json

$ openclaw memory status
Invalid config at ~/.openclaw/openclaw.json:\n- agents.defaults: Unrecognized key: "videoGenerationModel"
Memory Search (main)
...

$ openclaw tasks list
Invalid config at ~/.openclaw/openclaw.json:\n- agents.defaults: Unrecognized key: "videoGenerationModel"
Background tasks: 46
...
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug

Beta release blocker

No

Summary

In the installed OpenClaw 2026.4.5 CLI on macOS 26.3.1, openclaw config validate accepts a config containing agents.defaults.videoGenerationModel, but openclaw memory status and openclaw tasks list report the same key as unrecognized.

Steps to reproduce

  1. Use an ~/.openclaw/openclaw.json config that contains agents.defaults.videoGenerationModel.primary.
  2. Run openclaw config validate.
  3. Run openclaw memory status.
  4. Run openclaw tasks list.

Expected behavior

The same installed CLI release should treat agents.defaults.videoGenerationModel consistently across commands. A config that passes openclaw config validate should not be reported as invalid by openclaw memory status or openclaw tasks list.

Actual behavior

openclaw config validate prints Config valid: ~/.openclaw/openclaw.json.

openclaw memory status prints:

Invalid config at ~/.openclaw/openclaw.json:\n- agents.defaults: Unrecognized key: "videoGenerationModel"

and then continues to show memory status.

openclaw tasks list prints the same invalid-config message and then continues to show task output.

OpenClaw version

2026.4.5 (3e72c03)

Operating system

macOS 26.3.1

Install method

npm global via Homebrew Node; installed under /opt/homebrew/lib/node_modules/openclaw

Model

NOT_ENOUGH_INFO

Provider / routing chain

NOT_ENOUGH_INFO

Additional provider/model setup details

The config contains:

"agents": {
  "defaults": {
    "videoGenerationModel": {
      "primary": "xai-images/grok-imagine-video"
    }
  }
}

The same installed package also contains videoGenerationModel in shipped artifacts, including:

  • dist/zod-schema-C3jh3SvI.js
  • dist/runtime-schema-CZl4UsDY.js

Latest upstream source at a830f4de4b also contains videoGenerationModel in src/config/zod-schema.agent-defaults.ts and has a corresponding acceptance test in src/config/zod-schema.agent-defaults.test.ts.

Logs, screenshots, and evidence

$ /opt/homebrew/bin/openclaw --version
OpenClaw 2026.4.5 (3e72c03)

$ openclaw config validate
Config valid: ~/.openclaw/openclaw.json

$ openclaw memory status
Invalid config at ~/.openclaw/openclaw.json:\n- agents.defaults: Unrecognized key: "videoGenerationModel"
Memory Search (main)
...

$ openclaw tasks list
Invalid config at ~/.openclaw/openclaw.json:\n- agents.defaults: Unrecognized key: "videoGenerationModel"
Background tasks: 46
...

Impact and severity

Affected users/systems/channels: local CLI users running OpenClaw 2026.4.5 with agents.defaults.videoGenerationModel in config Severity: annoying and misleading Frequency: observed on every run of openclaw memory status and openclaw tasks list Consequence: users receive a false invalid-config warning even though openclaw config validate accepts the same file

Additional information

Latest upstream source in a separate dev checkout was updated to upstream/main commit a830f4de4b before inspection. That source tree already includes videoGenerationModel in the agent-defaults schema and related tests.

extent analysis

TL;DR

The most likely fix is to update the OpenClaw CLI to a version that includes the videoGenerationModel key in the agent defaults schema for openclaw memory status and openclaw tasks list commands.

Guidance

  • The issue seems to be a version mismatch between the openclaw config validate command and the openclaw memory status and openclaw tasks list commands, where the latter two do not recognize the videoGenerationModel key.
  • Verify that the videoGenerationModel key is indeed included in the schema used by openclaw memory status and openclaw tasks list by checking the source code or documentation.
  • Check if there are any updates available for the OpenClaw CLI that include the videoGenerationModel key in the agent defaults schema for all commands.
  • Consider filing an issue or pull request with the OpenClaw project to ensure consistency across all commands.

Example

No code snippet is provided as the issue seems to be related to a version mismatch rather than a code error.

Notes

The issue may be specific to the version of OpenClaw (2026.4.5) and the operating system (macOS 26.3.1) being used. The fact that the videoGenerationModel key is included in the shipped artifacts and the latest upstream source suggests that the issue may be resolved in a future update.

Recommendation

Apply a workaround by removing the videoGenerationModel key from the config file until an updated version of OpenClaw is available that includes this key in the agent defaults schema for all commands. This will prevent the false invalid-config warnings, but may not provide the desired functionality.

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 same installed CLI release should treat agents.defaults.videoGenerationModel consistently across commands. A config that passes openclaw config validate should not be reported as invalid by openclaw memory status or openclaw tasks list.

Still need to ship something?

×6

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

Back to top recommendations

TRENDING