openclaw - 💡(How to fix) Fix gog calendar integration may miss manually created Google Calendar events [1 participants]

Summary

OpenClaw daily briefing flows that rely on the gog skill for Google Calendar can miss events that were created manually in the Google Calendar UI.

In the affected setup, events created through gog calendar create are returned normally, but some manually created UI events are not returned by gog calendar events / gog calendar search for the same day.

This results in incomplete morning/evening calendar briefings.

Observed behavior

For the same calendar/day:

• a manually created UI event exists and is visible in Google Calendar
• a CLI-created event exists and is also visible in Google Calendar
• gog calendar events ... returns only the CLI-created event
• gog calendar search ... does not find the manual event either

Minimal reproduction

1. Create one event manually in the Google Calendar web/mobile UI, for example Manual Event.
2. Create another event on the same day via CLI, for example:

gog calendar create primary \
  --summary "CLI Event" \
  --from "2026-04-09T10:00:00+05:00" \
  --to "2026-04-09T10:30:00+05:00"

1. List that day's events:

gog calendar events primary \
  --from '2026-04-09T00:00:00' \
  --to '2026-04-09T23:59:59' \
  --json

1. Optionally search for the manual event title:

gog calendar search 'Manual Event' \
  --calendar primary \
  --from '2026-04-09T00:00:00' \
  --to '2026-04-09T23:59:59' \
  --max 10 \
  --json

Expected behavior

Both events visible in Google Calendar UI should be returned by gog for the same account/calendar/day.

Actual behavior

Only the CLI-created event is returned, while the manual UI-created event is missing.

Why this matters

OpenClaw automations that use the gog skill as the source of truth for daily briefings can produce incorrect output such as:

• "no events today"
• partial schedule summaries

Notes

This may be caused by one of the following:

• event type filtering differences between UI-created and CLI-created events
• date/time range filtering edge cases
• primary calendar resolution differences
• API/default query behavior in gog

No private account details, event titles, event IDs, or raw personal calendar payloads are included here, but I can provide sanitized follow-up output if needed.