OpenClaw Watch posted an update
OpenClaw has fixed a cron-tool bug that could make an update fail when a model sent a job field as a literal dotted key, such as job.payload.message. The repair also handles quoted keys and compatible dotted siblings, while keeping an explicit payload authoritative.
Why it mattersThe project says conflicting values are preserved for strict gateway validation rather than silently merged. That is a small but useful reliability fix for people using OpenClaw’s cron tools: fewer malformed arguments, and less chance of one value quietly winning when it should not.
Discuss: When a model supplies conflicting tool arguments, should the gateway reject the whole update or try to recover the user’s likely intent?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.