Skip to main content

Calendar cards

Cards are the planning layer of the calendar: a card anchors work to a day before (and after) the content exists. Each card has a title, notes, tagged teammates, linked content pieces, and a set of properties: date, category, and owner out of the box, plus any custom properties you define.

Drag a card to another day to move the plan; scheduled posts linked to the card shift by the same amount. Assigning a card notifies the assignee.

Creating cards​

Use the New button at the top right of the calendar (or + → New Card on any day cell) to open a blank card. Nothing is saved until you fill in a field; close an empty card and it never existed. Fill in anything without a title and the card saves as Untitled. Every card autosaves as you edit and can expand to a full page.

New cards land on the day you have navigated to (today by default); day-cell cards land on that day.

Card templates​

A template is a reusable preset card: title, date, category, owner, notes, and custom property values, saved once and applied in one click.

  • Apply a template from the ▾ next to the New button: search the list, click one, and a card is created with all its presets. New blank cards also offer the template list right in the notes area; press Enter or click into the notes to skip it.
  • Dynamic dates: when building a template, any date field can be set to Today (dynamic): it resolves to the current day each time the template is used.
  • Manage templates from the same dropdown: drag to reorder, and use each row's … menu to edit, duplicate, or delete. Editing a template only affects cards created from it afterwards; existing cards are copies, not links.
  • Workspaces can hold up to 100 templates.

Card properties​

Properties are the structured fields at the top of every card. Open calendar settings (the sliders icon next to the New button) to manage them:

  • Edit properties → Add property creates a new field on all cards. Types: Text, Number, Select, Multi-select, Date, Person (tags a workspace member), URL, and Checkbox. Select and multi-select options can be added, removed, recolored, and dragged into order; date properties have a display format.
  • Visible properties controls what shows on cards, workspace-wide, in two groups: Shown in calendar and Hidden in calendar. Visible properties appear on every card's calendar chip and in the card editor; hidden ones stay editable behind an N hidden properties disclosure inside the card, so their values are never lost.
  • The built-in Date, Category, and Owner properties can be shown or hidden like any other, but not renamed or deleted.
  • Deleting a custom property removes its values from every card and template.

View weekends​

Calendar settings also has a View weekends toggle. Turning it off hides the Saturday and Sunday columns on this device; cards on those days keep their dates and reappear when you toggle weekends back on.

Auto-schedule cards​

Recurring schedules lay their upcoming occurrences onto the calendar as placeholder cards, up to about a year ahead. A placeholder renders dimmed with a clock icon and its scheduled time, and its notes carry the generation prompt, so the whole future cadence is visible and adjustable on the calendar.

When an occurrence comes within two weeks, Reactor generates the piece and attaches it to the card:

  • Schedules set to draft leave the piece for your review.
  • Schedules set to ready also queue the post to publish automatically at the scheduled time.

After generation the card notes when the piece was created and whether it is publishing or waiting as a draft.

When something goes wrong​

  • Generation fails: the occurrence returns to placeholder and retries. After 3 failed attempts it is dropped and the owner gets a notification to generate that piece manually. (Quota-blocked occurrences are not dropped; they wait, and you are notified once per day.)
  • Publish fails: the linked post shows a red failed status on the card with the error, plus a publish-failed notification. Retry from the content editor.
  • Guard blocks it: auto-publishing re-checks the piece against the Anti-Slop Guard; if violations survive repair, the piece stays a draft instead of publishing and you get a guard-blocked notification to review it.

Statuses on a card​

Linked posts surface their state on the card: scheduled, publishing, published, failed, or canceled.

Over MCP​

Cards are fully manageable with the create_card, list_cards, update_card, and delete_card tools, and rescheduling a post keeps its linked card in sync automatically.

The property and template systems are exposed too:

  • list_card_properties / create_card_property / update_card_property / delete_card_property manage the property definitions.
  • list_card_templates / create_card_template / update_card_template / delete_card_template manage templates (including the dynamic "today" date).
  • create_card accepts a template_id plus custom properties; update_card merges property changes; list_cards returns each card's property values.

Agents can reference properties and select options by name (not just id), and people by email; invalid references return a specific error rather than being dropped.