Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 21, 2026, 8:20 AM ET / 12:20 UTC.

Summary
Keep open: current main and v2026.6.9 still lack the requested cron CLI fallback flags, and the open linked PR is the right implementation candidate to review before closing this issue.

Reproducibility: yes. at source level: current main has runtime/protocol support for payload.fallbacks, but the cron add/edit CLI registration does not expose or serialize fallback flags. This is a feature request rather than a failing existing CLI contract.

Root-cause cluster
Relationship: canonical
Canonical: #90302
Summary: This issue is the canonical request for cron CLI fallback flags, with one open candidate fix and two closed superseded attempts.

Members:

fixed_by_candidate: fix(cron): expose per-job fallbacks in CLI #93369 - The open PR uses closing syntax for this issue and implements the requested cron fallback CLI surface.
superseded: feat(cron): expose --fallbacks flag on cron add/create and edit commands (fixes #90302) #94653 - This closed unmerged PR targeted the same cron fallback CLI request before the fuller open implementation candidate.
superseded: feat(cron): expose --fallbacks option on cron create and edit commands #94918 - This closed unmerged PR targeted the same cron fallback CLI request before the fuller open implementation candidate.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Next step
The open linked PR already owns the implementation path, so maintainers should review, land, or decline that PR before changing this issue state.

Review details

Best possible solution:

Land #93369, or an equivalent complete patch, so CLI flags, clear semantics, docs, and focused cron coverage move together.

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

Yes at source level: current main has runtime/protocol support for payload.fallbacks, but the cron add/edit CLI registration does not expose or serialize fallback flags. This is a feature request rather than a failing existing CLI contract.

Is this the best way to solve the issue?

Yes: exposing the existing per-job payload field at the cron CLI boundary while aligning clear semantics with existing model/tools override patterns is the narrow maintainable path.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

Closing now would leave the requested CLI feature tracked only by an unmerged PR while current main and v2026.6.9 still lack the flags.

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

Label changes

Label changes:

add issue-rating: 🦞 diamond lobster: Current issue advisory state selects this label.
add clawsweeper:source-repro: Current issue advisory state selects this label.
add clawsweeper:fix-shape-clear: Current issue advisory state selects this label.
add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.
remove issue-rating: 🌊 off-meta tidepool: Current issue advisory state no longer selects this label.

Label justifications:

P3: This is a low-risk cron CLI ergonomics feature for an existing model fallback capability, not an urgent regression.
impact:auth-provider: The requested flag controls per-job model fallback routing for scheduled agent turns.

Evidence reviewed

What I checked:

Repository policy read: Root AGENTS.md was read fully; its linked-PR and fallback-surface guidance applies to keeping this issue open while an open closing PR owns the implementation path. (AGENTS.md:1, 12c34fc3a951)
Current cron add/create CLI gap: Current cron add registers adjacent --model and --tools options, but no --fallbacks option is registered. (src/cli/cron-cli/register.cron-add.ts:126, 12c34fc3a951)
Current cron add/create payload gap: The current agentTurn payload builder serializes model, thinking, timeout, light context, and toolsAllow, but not fallbacks from CLI input. (src/cli/cron-cli/register.cron-add.ts:253, 12c34fc3a951)
Current cron edit CLI gap: Current cron edit registers --model, --clear-model, --tools, and --clear-tools, but no --fallbacks or --clear-fallbacks controls. (src/cli/cron-cli/register.cron-edit.ts:114, 12c34fc3a951)
Runtime fallback contract exists: Cron agent-turn payloads already support optional per-job fallbacks?: string[], so the remaining gap is CLI exposure and clear/update semantics. (src/cron/types.ts:240, 12c34fc3a951)
Runtime fallback precedence exists: Cron runtime gives explicit payload fallbacks precedence over subagent/default fallback policy when executing isolated cron runs. (src/cron/isolated-agent/run-fallback-policy.ts:12, 12c34fc3a951)

Likely related people:

yinghaosang: Commit f902697 added the per-job cron payload.fallbacks contract this issue asks to expose in the CLI. (role: introduced payload fallback capability; confidence: high; commits: f902697bd5c4; files: src/cron/types.ts, src/cron/isolated-agent/run.payload-fallbacks.test.ts, src/cron/isolated-agent/run.ts)
andyk-ms: Commit 4d8c07b added the analogous list-style --tools cron CLI option in the same add/edit command surface. (role: adjacent CLI option contributor; confidence: medium; commits: 4d8c07b97c0b; files: src/cli/cron-cli/register.cron-add.ts, src/cli/cron-cli/register.cron-edit.ts, src/cron/normalize.ts)
ly-wang19: Commit 0888deb added cron edit --clear-model, the existing clear-override CLI pattern mirrored by the requested fallback clear control. (role: adjacent clear-override contributor; confidence: medium; commits: 0888debcd3eb; files: src/cli/cron-cli/register.cron-edit.ts, docs/cli/cron.md, docs/automation/cron-jobs.md)
849261680: Commit cfeaf68 changed cron payload clear contracts in the same schema/normalization/service area, and this person authored the open candidate fix PR. (role: recent adjacent contributor and candidate fix author; confidence: medium; commits: cfeaf6897fd8, 4d085807c845; files: packages/gateway-protocol/src/schema/cron.ts, src/cron/normalize.ts, src/cron/service/jobs.ts)
steipete: Commit 3ae5d33 refactored cron command registration and CLI tests that a complete fix exercises. (role: recent cron CLI/test refactor contributor; confidence: medium; commits: 3ae5d337997e; files: src/cli/cron-cli/register.cron-add.ts, src/cli/cron-cli/register.cron-edit.ts, src/cli/cron-cli.test.ts)

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Uh oh!

[Feature]: Expose --fallbacks on openclaw cron create/edit #90302

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions