Summary

openclaw cron edit exposes --model <model> but does not expose a matching --clear-model flag.

That means there is no obvious supported CLI way to remove an existing per-job payload.model override and fall back to inherited defaults.

Environment

• OpenClaw 2026.6.8 (844f405)
• CLI command: openclaw cron edit

Current behavior

openclaw cron edit --help includes:

--model <model>   Model override for agent jobs

But there is no corresponding:

--clear-model

The same help output already has parallel clear/unset flags for other fields, for example:

• --clear-agent
• --clear-session-key
• --clear-tools

Why this matters

During cron debugging, I needed to remove a job-level model pin so the cron job could inherit the configured default model/runtime path.

Because the CLI had no --clear-model, the only workable path was using the lower-level gateway cron.update route directly.

That is a gap in the supported ergonomic surface:

• users can set a model override from the CLI
• users cannot cleanly unset that same override from the CLI

Expected behavior

Add a matching flag:

openclaw cron edit <id> --clear-model

Expected semantics:

• remove payload.model from the cron job
• preserve the rest of the job payload unchanged
• allow the job to inherit the configured default model/runtime path

Suggested implementation

Mirror the existing clear-flag pattern already used by cron edit for other optional fields.

Why this matters operationally

Without --clear-model, a simple supported workflow becomes awkward:

1. a cron job gets pinned to a model
2. the operator later wants to revert to inherited defaults
3. the CLI cannot do the inverse of --model

That pushes users toward lower-level APIs or manual workarounds for something that should be a first-class edit operation.