Files

Jay Hickey 7e9be3c28c Update gog Calendar command date format to RFC3339

I am seeing instances where Clawdis is not including timezone in the gog calendar range requests. This results in a 400 bad request from the Google API, e.g.

```
gog calendar events primary --from 2026-01-02T00:00:00 --to 2026-01-03T23:59:59 --account <email>

Google API error (400 badRequest): Bad Request
```

While this is a valid ISO 8601 format, Google Calendar API requires a stricter RFC 3339 format like the following:

```
gog calendar events primary --from 2026-01-02T00:00:00Z --to 2026-01-03T23:59:59Z --account <email>

<calendar events listed successfully>
```

2026-01-03 02:30:32 +01:00

976 B

Raw Blame History

name, description, homepage, metadata

name

description

homepage

metadata

gog

Google Workspace CLI for Gmail, Calendar, Drive, and Contacts.

https://gogcli.sh

clawdis

emoji

requires

install

🎮

bins

gog

kind

formula

bins

label

brew

steipete/tap/gogcli

gog

Install gog (brew)

gog

Use gog for Gmail/Calendar/Drive/Contacts. Requires OAuth setup.

Setup (once)

gog auth credentials /path/to/client_secret.json
gog auth add you@gmail.com --services gmail,calendar,drive,contacts
gog auth list

Common commands

Gmail search: gog gmail search 'newer_than:7d' --max 10
Gmail send: gog gmail send --to a@b.com --subject "Hi" --body "Hello"
Calendar: gog calendar events <calendarId> --from <rfc3339> --to <rfc3339>
Drive: gog drive search "query" --max 10
Contacts: gog contacts list --max 20

Notes

Set GOG_ACCOUNT=you@gmail.com to avoid repeating --account.
Confirm before sending mail or creating events.

976 B Raw Blame History

gog

976 B

Raw Blame History