feat(cron): add agentId filtering to cron list#77602
Conversation
|
Codex review: passed. Summary Reproducibility: yes. The motivating behavior is source-reproducible on current main because cron tool, CLI, gateway schema, and service list paths do not accept or apply Real behavior proof Next step before merge Security Review detailsBest possible solution: Land the repaired PR through the normal automerge gates, preserving the source contributor credit and letting the merge close #77118. Do we have a high-confidence way to reproduce the issue? Yes. The motivating behavior is source-reproducible on current main because cron tool, CLI, gateway schema, and service list paths do not accept or apply Is this the best way to solve the issue? Yes. The PR uses an additive protocol field and CLI option, keeps unfiltered CLI behavior when What I checked:
Likely related people:
Codex review notes: model gpt-5.5, reasoning high; reviewed against a17d4371d101. |
dab0e0a to
068caa7
Compare
Adds optional agentId parameter to cron list action, allowing agents to filter cron jobs by their own agentId. This reduces noise in multi-agent setups where each agent sees all jobs across all agents. Changes: - Protocol schema: add optional agentId to CronListParamsSchema - Service types: add agentId to CronListPageOptions - Service ops: filter by agentId when provided - Gateway handler: pass through agentId param - Agent tool: auto-fill agentId from session context (like cron add) - CLI: add --agent <id> option to 'openclaw cron list' When called from an agent session without explicit agentId, the tool auto-fills it from the calling agent's session context. When called from CLI without --agent, all jobs are shown (backward compatible). Closes #77118
068caa7 to
35b692b
Compare
Summary
Closes #77118. This carries forward the implementation and credit from @zhanggttry in #77188.
Verification
ClawSweeper 🐠 replacement reef notes:
fish notes: model gpt-5.5, reasoning high; reviewed against dab0e0a.