gw-calendar

name	gw-calendar
description	Create, update, and list Google Calendar events via CLI. Handles Google Meet links, attendees, timezones, reminders, and locations. TRIGGERS: "calendar", "meeting", "schedule", "event", "google meet", "book a call", "availability", "schedule meeting", "create event", "update event", "reschedule", "change event", "modify event", "reminder"

Calendar

Account

Events are created on the default account unless you pass --account <name>. The default account is configurable — run gw auth list to see the accounts you have set up, and pass --account <name> to target a specific one.

Required Fields — always populate

Every create and update MUST include ALL of these fields. Never create a partial event.

Field	Flag	Default
Title	--title	— (required)
Start time	--start	— (required)
Duration	--duration	30 min
Description	--description	—
Location	--location	—
Attendees	--attendees	—
Reminders	--reminders	60,30,10 (auto)
Meet link	--meet	only when virtual

If the request is missing any of these details:

1. Search email first. Use the gmail skill to find the relevant thread:

   $CLI gmail list --query "subject:KEYWORD" --limit 5 --compact
   $CLI gmail get MESSAGE_ID --compact
   

   Extract: location/address, attendees, agenda/description, time details.
2. If email doesn't have it, ask the user. Do not guess or leave fields blank.

Examples of what to look for:

• "Let's meet at the office" → search email for the address, use as --location.
• "Call with Alex" → search email for Alex's email, full name for title, any agenda for description.
• "Coffee with investor" → search email for venue name + address, attendee email.
• In-person → --location with full address. Virtual → --meet flag. Hybrid → both.
• Workspace may auto-attach a Meet link on any event write (account "Automatically add Google Meet" setting), so an in-person event can sprout one after an unrelated update. That's not a bug. Pass --meet false to strip it (the CLI sends conferenceDataVersion=1, required for removal to take effect).

Defaults (auto-applied)

• Reminders: 60, 30, 10 min popup — set automatically on create. Do NOT change unless the user explicitly requests different reminders. Override: --reminders "120,15".
• Duration: 30 minutes.

Invocation

CLI="python3 ${CLAUDE_PLUGIN_ROOT}/cli/gw.py"

Commands

$CLI calendar create --title "Demo call" --start "2026-03-01T14:00" [--duration 30] [--meet] [--attendees "[e-mail],[e-mail]"] [--description "..."] [--location "123 Main St, City"] [--timezone "America/Denver"] [--reminders "60,30,10"] [--all-day --end "2026-03-03"] [--busy|--free]
$CLI calendar update --event-id "EVENT_ID" [--title "New title"] [--start "2026-03-01T15:00"] [--duration 60] [--meet true|false] [--attendees "[e-mail]"] [--description "..."] [--location "..."] [--timezone "America/Denver"] [--reminders "60,30,10"] [--busy|--free]
$CLI calendar list [--days 7] [--calendar all|CAL_ID] --compact
$CLI calendar calendars --compact
$CLI calendar get --event-id "EVENT_ID" [--calendar CAL_ID] --compact

list/get default to the primary calendar. Pass --calendar all to list to merge every accessible calendar (sorted by start), or --calendar CAL_ID to target a secondary calendar. Get a calendar's ID from calendar calendars. An event from a secondary calendar must be read with the same --calendar CAL_ID it was listed under.

Response Shapes (validated)

list: {"events":[{"id","calendar","title","start","end","location","attendees","meetLink","link"}],"count":7,"days":3,"calendars":["primary"]}

calendars: {"calendars":[{"id","summary","description","primary","accessRole","selected","timeZone"}],"count":3} — primary sorts first.

get: {"id","calendar","title","description","start","end","location","busy","status","organizer","attendees":[{"email","displayName","responseStatus","optional","organizer","self"}],"attendeeCount","meetLink","link"} — use this to read attendee RSVP status (accepted/declined/tentative/needsAction), which list flattens to bare emails. busy is true when the event blocks your free/busy time (opaque), false when it shows as free (transparent).

create: {"created":true,"id","title","start","end","location","busy","meetLink","link"}

update: {"updated":true,"id","title","start","end","location","busy","meetLink","link"}

Examples

# 30-min meeting with Meet link
$CLI calendar create --title "Intro call with Acme" --start "2026-04-07T10:00" --duration 30 --meet --attendees "[e-mail]"

# Change duration to 60 minutes
$CLI calendar update --event-id "abc123" --duration 60

# Reschedule and rename
$CLI calendar update --event-id "abc123" --title "Extended demo" --start "2026-04-07T11:00" --duration 60

# Multi-day all-day trip that blocks you as busy (--end is the last full day, inclusive)
$CLI calendar create --title "Tentative: offsite" --start "2026-07-02" --end "2026-07-03" --all-day --busy --location "Berlin, Germany"

# Flip an existing event to show as free (does not block free/busy)
$CLI calendar update --event-id "abc123" --free

# List next 3 days
$CLI calendar list --days 3 --compact

UI Verification

After create or update, verify the event looks correct in Google Calendar using Chrome DevTools MCP:

1. Open the event link returned in the link field:

   mcp__chrome-devtools__navigate_page → result.link
   

2. Take a screenshot and confirm: title, time, duration, location, attendees, and Meet link (if requested) all match.
3. If anything looks wrong, fix it with calendar update before reporting done.

Notes

• --duration defaults to 30 minutes.
• --timezone overrides local detection. Use IANA names (e.g. America/Denver).
• On Windows, set TZ env var — ZoneInfo("localtime") is unsupported.