Bee Box documentation · directory: https://beebox.run/docs/reference/cards/ · index: https://beebox.run/docs/reference/cards/index.md · root: https://beebox.run/llms.txt

# calendar Card

# Calendar Cards

A `.calendar.card` is one synced calendar. Its events are `.ics` files in
the card's attach folder, named `{date}_{title}_{id}.ics`. Sync with Google
is two-way: changes made here are sent on the next calendar sync.

```
_content/calendar/Family.calendar.card
_content/calendar/Family.attach/2026-06-25_Dentist_a1b2c3d4.ics
_content/calendar/Family.attach/stranded/      # edits Google would not take
```

## Adding or changing an event

To add an event to a calendar, write a new `.ics` file in **that calendar's
attach folder**; the folder decides the calendar. Any file name works: the
sync renames it to the standard name once Google has the event. To change an
event, edit its file. Changes reach Google on the next calendar sync. Use the
`calendar` skill for the file format.

Only `owner` and `writer` calendars (`google-calendar.access`) accept
changes. A `reader` calendar is read-only in Google: do not edit its files.

Do not move event files between calendar folders; it is not how an event
changes calendar, and the moved file is read as a new event.

## Frontmatter

Connector-managed; do not hand-edit. `title` is the calendar's name in Google
and `google-calendar:` is re-stamped on every sync. `syncing: false` means
the calendar was removed from the sync set: its files stay, Google's changes
no longer arrive, and edits made here are still sent.

## Body

The person's own notes about the calendar. The connector never writes it.

## The `contains:` field

Give this card a one-sentence `contains:` — the prime retrieval field for
`bbx search` and listings. How to write a good one (carry the information when
it's concise, never a list of parts, under 200 characters) is in the agent
guide's ABOUT_CARDS section.