Skip to content

[Bug]: Real-time logs of openclaw cron jobs are not displayed in the chat session of the webui #89064

Closed as not planned

Description

@Ninjaxsh

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

I forgot it's from which version.

Steps to reproduce

  1. add a cron job
  2. run it
  3. 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

Activity

  1. clawsweeper commented on Jun 1, 2026

    @clawsweeper
    Contributor

    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:

    • A live Ubuntu/npm/Control UI cron reproduction was not run in this read-only review, so runtime proof is still missing.
    • The desired UX is a maintainer decision: live cron progress could belong in the selected chat, the run-scoped cron session, Activity/tasks, or an explicit follow/watch mode.

    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:

    • node scripts/run-vitest.mjs ui/src/ui/controllers/chat.test.ts ui/src/ui/app-tool-stream.node.test.ts src/routing/session-key.test.ts src/cron/isolated-agent/run.session-key-isolation.test.ts
    • Live Control UI proof: create and run a cron job, watch the chosen live-progress surface while the assistant performs multiple operations, and verify progress appears before the terminal result.

    What I checked:

    • current cron run session key: Current main builds isolated cron output under a run-scoped child key when the base key starts with cron:, then reports that run key on cron execution events. (src/cron/isolated-agent/run.ts:636, e9b694ef9cd8)
    • current Web UI chat filter: Current main accepts chat events only when the event key is equivalent to the selected session key or selected global alias, so a cron run child key is not shown in another watched chat session. (ui/src/ui/controllers/chat.ts:510, e9b694ef9cd8)
    • current Web UI tool-stream filter: Current main also filters agent/tool events by host session key before rendering live tool cards or activity for the selected chat surface. (ui/src/ui/app-tool-stream.ts:317, e9b694ef9cd8)
    • current docs contract: Cron docs describe isolated cron chat delivery as agent direct sends plus final announce/webhook/none delivery, not live mirroring of every operation into the Web UI chat. Public docs: docs/cli/cron.md. (docs/cli/cron.md:87, e9b694ef9cd8)
    • latest release behavior: The v2026.6.9 tag has the same run-scoped cron key construction and Web UI session filters, so the requested live-log behavior is not already shipped fixed. (src/cron/isolated-agent/run.ts:636, c645ec4555c0)
    • history provenance: Blame and history tie the current run-key and UI-filter lines to recent snapshot/release commits, with older isolated-cron seams introduced in April cron refactors. (src/cron/isolated-agent/run.ts:636, 273eb888749f)

    Likely related people:

    • vincentkoc: Current blame and recent release/current-main history carry the cron run-key and Web UI session-filter behavior in the central files. (role: recent area contributor; confidence: medium; commits: 273eb888749f, c645ec4555c0; files: src/cron/isolated-agent/run.ts, ui/src/ui/controllers/chat.ts, ui/src/ui/app-tool-stream.ts)
    • steipete: History ties Peter Steinberger to the isolated cron execution seam and phase split that the run-scoped cron behavior builds on. (role: feature-history contributor; confidence: high; commits: 91d20781ed03, bbb73d3171e5; files: src/cron/isolated-agent/run.ts, src/cron/isolated-agent/run-session-state.ts)
    • tyler6204: History shows earlier cron scheduling, delivery, and isolated announce hardening work in the same cron runtime area. (role: cron feature-history contributor; confidence: medium; commits: 8fae55e8e057, d90cac990c8f; files: src/cron/isolated-agent/run.ts, src/cron/service/timer.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.
  2. added
    P2Normal backlog priority with limited blast radius.
    impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.
    issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.
    clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.
    clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.
    clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.
    clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.
    on Jun 1, 2026
  3. openclaw-barnacle commented on Jul 6, 2026

    @openclaw-barnacle

    This issue has been automatically marked as stale due to inactivity.
    Please add updates or it will be closed.

  4. openclaw-barnacle commented on Jul 14, 2026

    @openclaw-barnacle

    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.

  5. locked as resolved and limited conversation to collaborators on Aug 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.bugSomething isn't workingclawsweeper:needs-live-reproClawSweeper 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:needs-product-decisionClawSweeper 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.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.staleMarked as stale due to inactivity

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions