Google Calendar

Calendar adds meeting context to your work timeline: what you discussed, who you met with, and how much time went to meetings vs. focused work.

Connect

devrecall auth google

Opens a browser for Google OAuth via relay.devrecall.dev. Read-only scope — DevRecall literally cannot create, modify, or delete events.

Tokens (access + refresh) are stored in ~/.devrecall/tokens/google.json (0600). The agent refreshes the access token automatically using the refresh token.

What gets collected

Field	Source
Meeting title	Event `summary`
Start / end / duration	Event `start.dateTime` / `end`
Attendees + status	`attendees[].email` + `responseStatus`
Organizer	`organizer.email`
Location / video link	`location`, `conferenceData`
Recurrence	`recurringEventId`, `RRULE`
Your response	`responseStatus` (accepted/declined/tentative)

Declined meetings are tracked separately — useful for showing how you prioritized your time.

Auto-classification

DevRecall labels meetings to make standups read better:

Pattern	Label
1–2 attendees	`1:1`
”standup”, “daily”, “sync” in title	`standup`
”sprint”, “retro”, “planning” in title	`ceremony`
”interview” in title	`interview`
”focus”, “no meetings”	`focus_block`
3+ attendees, no clear pattern	`group_meeting`

focus_blocks are skipped in standups.

Required scopes

Scope	Purpose
`https://www.googleapis.com/auth/calendar.readonly`	Read calendars + events
`https://www.googleapis.com/auth/userinfo.email`	Identity linking

Sync efficiency

Google Calendar’s syncToken API gives true incremental sync. After the initial fetch, daily syncs are typically 1–2 API calls. Calendar’s quota is 1,000,000 queries/day per project — you’re nowhere near it.

Microsoft Outlook / Office 365

Not yet — planned for a later release. Same shape as Google Calendar via the Microsoft Graph API.