Calendar
A box is a directory of your data, kept under version control with a full history of changes (using git); a card is a markdown file with a structured header; the agent is the coding agent (Claude Code or Codex) that operates the box. The calendar connector syncs Google Calendar into the box as plain calendar files.
What it does for you
- Pulls your Google Calendar events into the box as individual
.icsfiles, one per event, readable and editable as plain text. - Lets the agent read your agenda from the box's own copy instead of calling Google every time.
- Supports creating, editing, and deleting events by editing files, which push back to Google on sync.
- Recurring events are stored as one file with a recurrence rule, so a weekly meeting is not hundreds of separate files.
What it needs
A Google account, connected by signing in with your Google account and a one-time setup, shared with the Gmail and Drive connectors. See the install directory: ../install/index.md.
How it works, briefly
Events are stored in the box as individual .ics files (kept in _content/calendar/, for the curious). Pull is the well-exercised direction: sync brings Google's events into the box. Local edits, locally-created events, and deletions are pushed back to Google during sync, but this push path and automatic scheduled sync are both less exercised than the pull side. There is no calendar-month view built in; you look up events by asking the agent rather than browsing a calendar page.
Limits
Scheduled auto-sync is off by default, so a calendar left alone will not stay current on its own. The documentation describes the push-back path as having had little real-world use, so treat locally-made changes reaching Google as less reliable than the reverse.
Go deeper