Repository navigation
Closed as not planned
Closed as not planned
Copy link
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.bugSomething isn't workingSomething isn't workingclawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.ClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.Good issue quality with a plausible reproduction path needing some confirmation.staleMarked as stale due to inactivityMarked as stale due to inactivity
Description
Bug type
Behavior bug (incorrect output/state without crash)
Beta release blocker
No
Summary
I forgot it's from which version.
Steps to reproduce
- add a cron job
- run it
- watch the chat session
Expected behavior
After each operation is completed by the assistant, the execution logs is immediately output in the chat session
Actual behavior
Output the assistant execution log only after the task is completely completed
OpenClaw version
2026.5.28
Operating system
ubuntu 24.04
Install method
npm global
Model
qwen 3.5-flash
Provider / routing chain
qwen
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response
Reacted by clawsweeper
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.bugSomething isn't workingSomething isn't workingclawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.ClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.Good issue quality with a plausible reproduction path needing some confirmation.staleMarked as stale due to inactivityMarked as stale due to inactivity
Type
Fields
Priority
None yet
Activity
clawsweeper commentedon Jun 1, 2026
Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 21, 2026, 5:02 AM ET / 09:02 UTC.
Summary
Keep open. Current main and v2026.6.9 still do not define or implement live cron-operation streaming into the watched Web UI chat; source shows run-scoped cron events filtered away from other selected sessions, and maintainer UX direction is needed before repair.
Reproducibility: yes. at source level: current main emits isolated cron activity under a run-scoped session key while the Web UI chat/tool handlers filter against the selected session key. A live Ubuntu/npm Web UI cron reproduction has not been run in this read-only review.
Next step
Manual review is needed because the source path is clear but the item has product-decision and live-repro blockers before a safe fix PR can be scoped.
Review details
Best possible solution:
Define the intended live-progress destination for cron runs, then align cron event routing, Web UI stream filtering, docs, and focused tests with that contract.
Do we have a high-confidence way to reproduce the issue?
Yes at source level: current main emits isolated cron activity under a run-scoped session key while the Web UI chat/tool handlers filter against the selected session key. A live Ubuntu/npm Web UI cron reproduction has not been run in this read-only review.
Is this the best way to solve the issue?
Unclear; streaming into the watched chat may be useful, but current code and docs treat cron runs as isolated automation with final-result delivery, so maintainers should choose the intended live-progress destination first.
AGENTS.md: found and applied where relevant.
Remaining risk / open question:
Codex review notes: model internal, reasoning high; reviewed against e9b694ef9cd8.
Label changes
Label justifications:
P2: The issue affects a bounded cron observability workflow without evidence of data loss, security exposure, or core runtime outage.impact:other: The concrete impact is delayed visibility into scheduled-agent execution progress, which is maintainer-visible but outside the more specific owned impact labels.Evidence reviewed
Acceptance criteria:
What I checked:
src/cron/isolated-agent/run.ts:636, e9b694ef9cd8)ui/src/ui/controllers/chat.ts:510, e9b694ef9cd8)ui/src/ui/app-tool-stream.ts:317, e9b694ef9cd8)docs/cli/cron.md. (docs/cli/cron.md:87, e9b694ef9cd8)src/cron/isolated-agent/run.ts:636, c645ec4555c0)src/cron/isolated-agent/run.ts:636, 273eb888749f)Likely related people:
src/cron/isolated-agent/run.ts,ui/src/ui/controllers/chat.ts,ui/src/ui/app-tool-stream.ts)src/cron/isolated-agent/run.ts,src/cron/isolated-agent/run-session-state.ts)src/cron/isolated-agent/run.ts,src/cron/service/timer.ts)How this review workflow works
@clawsweeper re-reviewcomments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.@clawsweeper re-reviewor@clawsweeper re-runon an open PR or issue to request a fresh review only.@clawsweeper reviewto request a fresh review only.@clawsweeper autofix,@clawsweeper automerge,@clawsweeper fix ci, or@clawsweeper address review.@clawsweeper explainto ask for more context, or@clawsweeper stopto stop active automation.openclaw-barnacle commentedon Jul 6, 2026
This issue has been automatically marked as stale due to inactivity.
Please add updates or it will be closed.
openclaw-barnacle commentedon Jul 14, 2026
Closing due to inactivity.
If this is still an issue, please retry on the latest OpenClaw release and share updated details.
If you are absolutely sure it still happens on the latest release, open a new issue with fresh steps to reproduce.