OpenClaw April 6 Release: Built-In Video/Music Tools + Safer Config Migrations for Self-Hosters

OpenClaw's latest release (published April 6) shipped a few changes that matter immediately for people running personal or self-hosted agent stacks.

What changed (high-impact items)

1) Native media generation tools are now first-class

The release adds built-in video_generate and music_generate tools, plus bundled provider wiring (including ComfyUI workflow support).

Why this matters: you can now keep common media workflows inside your existing OpenClaw tool/approval pipeline instead of bolting on one-off scripts.

2) Config cleanup is now stricter (with migration support)

Legacy public config aliases were removed in favor of canonical config paths. Existing installs keep load-time compatibility, and migration help is available through doctor/fix flows.

Why this matters: fewer ambiguous config surfaces, but operators should run a config health pass before or immediately after upgrade.

3) Background task infrastructure keeps hardening

Across recent updates, task execution and lifecycle visibility continue converging around a unified control plane for cron/subagent/background runs.

Why this matters: easier operational debugging and less "where did this run come from?" confusion when multiple automations are active.

Practical upgrade checklist (30 minutes)

1. Read release notes first and identify any legacy config keys in your deployment.
2. Run openclaw doctor and apply suggested config migrations before peak usage hours.
3. Smoke-test approvals (especially exec/tool approvals) from your real chat surface.
4. Validate one media workflow end-to-end (video_generate or music_generate) to confirm provider credentials and output delivery.
5. Check background task visibility so cron/subagent runs appear where your team expects.

Sources used for verification

• Official OpenClaw GitHub releases page (latest April 6 release notes and change list).
• ReleaseBot OpenClaw release tracker (independent aggregation showing the same release wave and breaking-change themes).

If you maintain a production-ish self-hosted setup, this is a "upgrade soon, but test deliberately" release: useful new capabilities, plus config/security posture tightening that rewards a quick checklist-driven rollout.