Best possible solution:

Land this as a focused cron feature after normalizing the filter value consistently and adding regression tests plus docs/changelog entries.

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

Yes. Source inspection shows current main has no agentId field in cron.list, and the PR defect is reproducible from code because cron add/edit normalize stored agent IDs while the new list filter compares the raw requested value.

Is this the best way to solve the issue?

No, not yet. The API shape is reasonable, but the maintainable fix should normalize the requested agent ID before filtering and ship with tests, docs, and changelog coverage.

Full review comments:

• [P2] Normalize agent IDs before filtering cron jobs — src/cron/service/ops.ts:289-291
  The new filter compares the requested agentId to job.agentId verbatim. Cron creation and edits canonicalize IDs, so openclaw cron add --agent Ops ... stores ops but openclaw cron list --agent Ops would return no jobs; normalize the list filter before comparing and cover that path.
  Confidence: 0.9
• [P3] Add the required docs and changelog entry — src/cli/cron-cli/register.cron-add.ts:48
  This exposes a user-facing CLI/tool/protocol feature, but the PR changes only source and generated protocol files. Add the required changelog entry plus cron docs for cron list --agent, and include focused regression coverage for the new behavior.
  Confidence: 0.86

Overall correctness: patch is incorrect
Overall confidence: 0.87

Acceptance criteria:

• pnpm test src/cron/service.list-page-sort-guards.test.ts src/gateway/protocol/cron-validators.test.ts src/gateway/server.cron.test.ts src/agents/tools/cron-tool.test.ts src/cli/cron-cli.test.ts
• pnpm exec oxfmt --check --threads=1 src/cron/service/ops.ts src/cron/service/list-page-types.ts src/gateway/protocol/schema/cron.ts src/gateway/server-methods/cron.ts src/agents/tools/cron-tool.ts src/cli/cron-cli/register.cron-add.ts docs/cli/cron.md docs/automation/cron-jobs.md CHANGELOG.md
• pnpm check:changed

What I checked:

• Current main cron tool list is unfiltered: Current main sends only includeDisabled from the agent cron tool for the list action, so the linked feature gap is real on main. (src/agents/tools/cron-tool.ts:656, fcb396bf6589)
• Current main protocol lacks agentId list parameter: CronListParamsSchema accepts paging/query/sort fields but no agentId, matching the linked issue's report. (src/gateway/protocol/schema/cron.ts:282, fcb396bf6589)
• PR filter compares raw agent IDs: The PR adds an opts.agentId filter in listPage, but the comparison is against job.agentId verbatim rather than the normalized form used when jobs are created or patched. (src/cron/service/ops.ts:289, d50cfbb7ae2f)
• Stored cron job agent IDs are normalized: Cron job creation stores agentId through normalizeOptionalAgentId, and CLI add sanitizes --agent, so list filtering must normalize the requested filter consistently. (src/cron/service/jobs.ts:591, fcb396bf6589)
• Cron docs do not cover list filtering: The current cron CLI docs cover cron list and agent retargeting for edit/add, but not a cron list --agent filter; the PR diff also contains no docs, tests, or changelog files. Public docs: docs/cli/cron.md. (docs/cli/cron.md:222, fcb396bf6589)

Likely related people:

• Peter Steinberger: Local history shows multiple recent cron service and CLI refactors touching the relevant normalization and cron CLI surfaces. (role: cron feature/refactor maintainer; confidence: high; commits: e66c418c4533, b1c30f0ba9b8, e86b38f09d85; files: src/cron/service/ops.ts, src/cron/normalize.ts, src/cli/cron-cli/register.cron-add.ts)
• Tyler Yust: A prior cron consolidation commit touched the cron service, gateway handler, CLI tests, and cron docs, which overlap the PR's user-facing behavior and documentation needs. (role: adjacent cron delivery/docs maintainer; confidence: medium; commits: 38543d819690; files: src/cron/service/ops.ts, src/gateway/server-methods/cron.ts, src/cli/cron-cli.test.ts)
• Vincent Koc: Current-main blame in this checkout points the central cron list, cron tool, CLI list, and protocol schema lines to a recent broad commit; the trail is less specific because that commit is not cron-focused. (role: recent current-main maintainer; confidence: low; commits: 8a8a12559df0; files: src/cron/service/ops.ts, src/agents/tools/cron-tool.ts, src/cli/cron-cli/register.cron-add.ts)

Remaining risk / open question:

• List filtering will silently miss jobs when callers pass non-canonical agent IDs such as different casing or extra invalid characters.
• The user-facing CLI/tool/protocol change has no regression coverage, docs, or changelog entry in the proposed diff.

Codex review notes: model gpt-5.5, reasoning high; reviewed against fcb396bf6589.