ZeroClaw proposes a guided schedule editor, separate from delivery guarantees

ZeroClaw's proposed schedule editor turns a compact but error-prone expression into an ordinary form. The September 7 PR adds labelled minute, hour, day, month and weekday fields, validation and a human-readable description before submission. Its scope is deliberately frontend-only. A separate tracker opened that day coordinates delivery and cron-outcome fixes, making this a useful example of usability work that does not pretend to solve runtime reliability.

The facts

- The editor assembles five local fields into the same single schedule string that the existing API already accepts. - The proposed default is 0 9 * * 1-5, and cronstrue supplies a local plain-English read-back of valid expressions. - Invalid values produce field-level error states, accessible validity announcements and a disabled submit action rather than an unchecked save. - The PR explicitly leaves HTTP shapes, persistence, database schema, timezone handling and scheduler behavior unchanged. - The separate September 7 tracker coordinates false-send success, duplicate replies, skipped or unowned cron outcomes and agent delivery instructions. - That tracker excludes a new durable retry or outbox system and notes that a concurrent cron-module extraction must preserve accepted behavior.

Why it matters

A guided form can prevent a malformed schedule, but a well-formed schedule can still fail to run or deliver. Keeping those claims separate is valuable for unattended automation, where a green configuration screen is easily mistaken for an operational receipt. ZeroClaw's paired work shows two different owner responsibilities: the dashboard explains what the user asked for, while the scheduler and channels must record what actually happened. The absence of timezone changes is particularly important; a readable expression does not establish that the operator and daemon mean the same local hour.

Current

Inspected on 2026-09-08. The ZeroClaw stable-release baseline is v0.8.5 published 2026-09-05T07:31:19Z. The main source was open when captured. Release metadata is a version boundary, not evidence that an open proposal has shipped.

Evidence

The primary source is zeroclaw-labs/zeroclaw PR #10698 (https://github.com/zeroclaw-labs/zeroclaw/pull/10698). Supporting context comes from zeroclaw-labs/zeroclaw issue #10685 (https://github.com/zeroclaw-labs/zeroclaw/issues/10685); ZeroClaw — current project README (https://raw.githubusercontent.com/zeroclaw-labs/zeroclaw/master/README.md). The linked records were inspected directly; related project records are not independent confirmations.

Operator take

Evaluate the form with keyboard-only input, an invalid minute and an edited recurring interval, then inspect the exact saved expression. Separately test a scheduled run at a known time and check its destination receipt. If a job is skipped or lacks an owner, the outcome should remain distinguishable from a completed job whose message failed. The tracker also protects against duplicate suppression based on an attempted send rather than a successful identical send. These are practical acceptance criteria, not reasons to conflate the proposals into one shipped feature. The editor can reduce setup mistakes while the runtime changes are still under review; neither a UI build nor a four-PR coordination table proves end-to-end unattended delivery.

Caveat

Both the guided editor and delivery tracker were open when inspected. Browser and build checks are reported by the editor's author, not reproduced here. The form does not change timezone semantics, and the tracker is not a delivered durable-retry design.