Greptile Summary

This PR adds optional chaining guards at two startsWith call sites in the cron runtime to prevent a TypeError crash when a CronJob has payload.kind='agentTurn' but sessionTarget is unexpectedly undefined at runtime (e.g., from pre-normalizer persisted data). The type definition (CronSessionTarget) does not include undefined, but the defensive guard is warranted because persisted JSON from older format versions could produce jobs without sessionTarget before normalization defaults were applied.

Confidence Score: 5/5

Safe to merge — the changes are minimal, targeted, and correctly prevent a crash without altering any other behavior.

Both changes are correct: the delivery-plan.ts guard evaluates to false when sessionTarget is undefined, keeping isIsolatedAgentTurn false and the delivery mode as none. The server-cron.ts guard is safe because the if body (which calls .slice(8)) is only entered when startsWith returned true, proving sessionTarget is defined. No P0/P1 findings.

No files require special attention.

_{Reviews (1): Last reviewed commit: "fix(cron): guard against undefined sessi..." | Re-trigger Greptile}

+1 — confirmed exposure. We run scheduled cron jobs on 4 OpenClaw 2026.4.5 agents (AI news delivery, regulation report sync, file scanner) with payload.kind: "agentTurn". Our cron job specs do include sessionTarget, but this is a defensive fix that prevents a crash from an otherwise-valid config shape.

We've separately seen the #62876 / #62265 crash class (agent listener outside active run) in cron contexts, and having the cron runtime crash on a missing field before it even starts the job makes debugging harder.

Good fix — optional chaining here is the right approach.

Environment: 4 sandboxes, OpenClaw 2026.4.5, multiple cron jobs with exec tools (Typst, TTS).