OpenClaw Self-Corrected a Timezone Mistake: Critique Loop Catches Calendar Errors

A Reddit user reports that OpenClaw's create-critique-revise loop caught multiple errors when consolidating scattered family plans into a single ICS calendar file. The inputs included an Excel sheet, text threads with tentative plans, and old calendar exports with outdated dates.

Key Findings from the Self-Correction

During the critique stage, OpenClaw identified and fixed three specific issues:

• Wrong timezone: A son's departure time was recorded in his local time but needed to be in Eastern time. The critiquer caught this mismatch.
• Wrongly applied recurring rule: A one-off coffee meetup had incorrectly inherited a recurring rule from a similar recurring coffee event for a different person at the same location. The critique flagged this and removed the recurrence.
• Stale date from an old export: An old calendar export contained a wrong date for a birthday party. The first pass used the old date, but the critique cross-referenced against the main planning sheet and corrected it to the right date.

Privacy Handling

The user noted that personal contextual notes were automatically excluded from the calendar files without explicit exclusion instructions. This suggests OpenClaw distinguishes between planning context and output content.

Practical Takeaway

The critique stage is not just a formality—it caught concrete errors that would have resulted in missed flights or double-booking. For developers building calendar workflows, ensuring the loop actively cross-references multiple data sources is key.