@agent-native/core 0.172.3 → 0.172.6

package/docs/content/template-calendar-features.mdx

@@ -0,0 +1,276 @@
+---
+title: "Calendar: Features"
+description: "Every core Calendar feature, including views, availability, finding time, and booking links, with setup steps for each."
+---
+
+# Features
+
+Every core Calendar feature: how it works, and how to set it up. See
+[Calendar](/docs/template-calendar) for the overview and
+[Talk to the Agent](/docs/template-calendar-agent) for the full list of
+prompts.
+
+## Calendar views
+
+<Video
+  src="https://cdn.builder.io/o/assets%2FYJIGb4i01jvw0SRdL5Bt%2Fd033f1071872452687ea570ed2ab6da3?alt=media&token=c6318aee-94cc-4898-be16-32b8fbf4fb2f&apiKey=YJIGb4i01jvw0SRdL5Bt"
+  alt="A brief tour of the calendar view."
+  caption="A tour of the calendar view, including viewing another person's calendar and adding events."
+  autoplay={true}
+  loop={true}
+/>
+
+Switch between day, week, and month view from the toolbar. Every view reads
+your real, connected Google Calendar. Nothing is cached or synthetic.
+
+- **Multiple accounts** show in the same grid, color-coded, if you connect
+  more than one Google account (work + personal).
+- **Read-only ICS/`webcal://` feeds** cover things like company holidays, a
+  conference schedule, or a teammate's public calendar. They mix into the
+  same view with their own color, though you can't edit events that come
+  from a feed.
+- **Overlay a teammate's calendar** so their events show alongside yours,
+  each in their own color. This helps when a manager needs to check a direct
+  report's schedule.
+- **Attendee timezones** show a guest's local start time when Google reports
+  it, or from a saved per-guest override when it doesn't.
+- **Working locations** (home, office, elsewhere) show as a real status, not
+  a generic all-day event, and never block your availability. **Recurring
+  events** are supported end to end. Edit a single occurrence or the whole
+  series.
+
+<Callout tone="warning">
+
+If part of your schedule fails to load, whether one account's token expired
+or a feed URL times out, the app tells you which source failed instead of
+quietly showing an empty day. A blank calendar and a broken connection look
+different on purpose, so you never mistake "nothing loaded" for "nothing
+scheduled."
+
+</Callout>
+
+<Steps>
+
+### Connect your calendar
+
+Open **Settings**, click **Connect Google Calendar**, and approve. Connect
+more accounts the same way if you want personal + work overlayed.
+
+### Subscribe to a read-only feed
+
+In **Settings → External Calendars**, paste an ICS or `webcal://` URL.
+
+### Overlay a teammate's calendar
+
+Ask the agent to "Add Priya's calendar to my view in blue," or add them from
+**Settings → Overlays**.
+
+</Steps>
+
+## Finding time
+
+Ask the agent to find time and it checks your availability and your real
+Google Calendar events. When you name other people, it also checks their
+free/busy status, then proposes concrete slots. Once you pick one, the agent
+books it directly on Google Calendar.
+
+When you're scheduling with someone new, search by name or email instead of
+typing an exact address. Calendar searches your Google Contacts plus your
+Workspace directory, so you can ask "who is Dana at Acme" or "find people
+named Priya" and get real matches to pick from.
+
+<Diagram id="doc-block-calendar3" title="From availability to a booked event" summary="The agent combines your availability rules, your existing events, and (when named) other attendees' free/busy before proposing slots.">
+
+```html
+<div class="diagram-flow">
+  <div class="diagram-col">
+    <div class="diagram-box">
+      Your availability<br /><small class="diagram-muted"
+        >weekly hours, buffer, notice</small
+      >
+    </div>
+    <div class="diagram-box">
+      Existing events<br /><small class="diagram-muted"
+        >Google Calendar, live</small
+      >
+    </div>
+    <div class="diagram-box">
+      Attendees' free/busy<br /><small class="diagram-muted"
+        >when you name people</small
+      >
+    </div>
+  </div>
+  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
+  <div class="diagram-panel center">
+    <span class="diagram-pill accent">Find a time</span
+    ><small class="diagram-muted">candidate slots</small>
+  </div>
+  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
+  <div class="diagram-box">You pick one</div>
+  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
+  <div class="diagram-box">Event created on Google Calendar</div>
+</div>
+```
+
+```css
+.diagram-flow {
+  display: flex;
+  align-items: center;
+  gap: 12px;
+  flex-wrap: wrap;
+}
+.diagram-flow .diagram-col {
+  display: flex;
+  flex-direction: column;
+  gap: 10px;
+}
+.diagram-flow .diagram-arrow {
+  font-size: 22px;
+  line-height: 1;
+}
+.diagram-flow .center {
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+  gap: 4px;
+}
+```
+
+</Diagram>
+
+<Steps>
+
+### Ask for a slot
+
+"Find a 1-hour slot next week with Sam and Priya."
+
+### Pick one
+
+The agent proposes concrete slots. Pick one in chat, or from the suggested
+options in the UI.
+
+### It's booked
+
+The agent creates the event directly on Google Calendar and it shows up in
+your view immediately.
+
+</Steps>
+
+## Booking links
+
+Booking links are public pages where anyone can pick a time and book it
+directly onto your calendar. This is the Calendly-style part of Calendar: set
+up meeting types, the availability they draw from, and track who books.
+
+### Meeting Types
+
+A meeting type is one specific booking link, like "15 min intro" or "30 min
+demo," each with its own duration, fields, and conferencing choice.
+
+<Steps>
+
+### Create a meeting type
+
+Give it a title and duration (like "15 min intro" at 15 minutes), then ask
+the agent or click **New booking link**.
+
+### Add options
+
+Set alternate durations so a visitor can choose 15, 30, or 60 minutes on the
+same link, custom fields to collect a company name or topic, a conferencing
+choice (Google Meet, Zoom, or a custom link), a color, and required
+co-hosts, other people who must also be free before a slot is offered. When
+someone books, everyone (you and your co-hosts) gets invited to the resulting
+Google Calendar event.
+
+### Connect Zoom (optional)
+
+Google Meet needs no setup. It's added the same way any Google Calendar
+invite gets a Meet link. For Zoom, connect your account once from
+**Settings**. After that, any meeting type set to Zoom creates a real Zoom
+meeting for each new booking and attaches the join link to the confirmation.
+
+### Share it
+
+Share the public URL anywhere. Grant a teammate viewer/editor/admin access
+from the link's **Share** menu if they should help manage it too. That's
+separate from public booking access, which anyone with the URL always has
+while the link is active.
+
+</Steps>
+
+Every meeting type has a public URL at `/book/{your-booking-name}/{slug}`,
+for example `/book/steve/30min`. Your booking name is generated automatically
+from your email the first time you create a link, and you can change it later
+from Settings (up to three times every 30 days, since it's part of every
+public link you've shared).
+
+<Video
+  src="https://cdn.builder.io/o/assets%2FYJIGb4i01jvw0SRdL5Bt%2F3dda132ad91b44dfa11c9d4e4b9e1b79?alt=media&token=b25577a1-ef91-48f8-a474-e5a39b246c25&apiKey=YJIGb4i01jvw0SRdL5Bt"
+  alt="Video showing how to create a new booking meeting type."
+  caption="Video showing how to create a new booking meeting type."
+  autoplay={true}
+  loop={true}
+/>
+
+- **Renaming a meeting type**: change its URL slug at any time, for example
+  from `/book/steve/into-call` to `/book/steve/intro`. The old URL keeps
+  working: visitors who still have it are automatically forwarded to the new
+  one, so nothing you've already shared breaks.
+
+### Availability
+
+Availability is a weekly schedule: which days you work and what hours you're
+open on each one, plus your timezone. On top of that you can set **buffer
+time** between meetings so back-to-back bookings don't happen, **minimum
+notice** so people can't book you five minutes from now, **how far ahead**
+people can book (advance window), and a **default slot length** for new
+meeting types.
+
+The agent reads the same schedule the UI edits, so "set my hours to 9-5
+weekdays" and dragging the sliders in the Availability tab produce the same
+result.
+
+<Steps>
+
+### Set your weekly hours
+
+Switch to the **Availability** tab and toggle on the days and hours you're
+open, per day if needed.
+
+### Add buffer and notice
+
+Set **buffer time** between meetings and a **minimum notice** window so
+people can't book you five minutes from now.
+
+### Set your advance window and default slot length
+
+Choose how far ahead people can book, and the default duration new meeting
+types start with.
+
+</Steps>
+
+Or just ask the agent: "Block Friday afternoons on my availability."
+
+### Bookings
+
+A visitor picks an available time from your real availability, fills in
+their name, email, and any custom fields you added, then confirms. They get a
+confirmation with a private manage link. No sign-in is required, since the
+link itself is the credential.
+
+- **Managing bookings**: you (the host) see every booking, past and
+  upcoming, filtered by all, confirmed, or cancelled, in the **Bookings** tab.
+- **Rescheduling or cancelling**: visitors use their manage link to move to
+  a different open slot or cancel outright, without needing an account. You
+  can also cancel a booking yourself from the **Bookings** tab.
+
+Or ask the agent: "Show me this week's bookings."
+
+## What's next
+
+- [**Calendar**](/docs/template-calendar) — the overview and getting-started steps
+- [**Talk to the Agent**](/docs/template-calendar-agent) — every prompt by task, application state, and Extensions
+- [**Calendar in a Multi-App Workspace**](/docs/template-calendar-integrations) — integration strategies and connecting to Dispatch
+- [**Developer Guide**](/docs/template-calendar-developers) — the actions and data model behind these features
+- [**Sharing**](/docs/sharing) — the share-grant model booking links build on

package/docs/content/template-calendar-integrations.mdx

@@ -0,0 +1,78 @@
+---
+title: "Calendar in a Multi-App Workspace"
+description: "How Calendar connects to Dispatch and other apps, the real events other apps can automate against, and natural-language delegation across a multi-app workspace."
+---
+
+# Calendar in a Multi-App Workspace
+
+Calendar is one app among many in a [Dispatch](/docs/template-dispatch)
+workspace. This page covers what that actually means in practice: how the
+connection works, and concrete ways other apps can act on your calendar or
+react to what happens on it. See [Calendar](/docs/template-calendar) for the
+overview.
+
+## How Calendar connects to Dispatch
+
+Whether this is automatic depends on how Calendar and Dispatch were set up
+together, not on whether either one is hosted or running locally.
+
+### Same workspace: automatic
+
+If Calendar and Dispatch were generated or added together into one Agent
+Native workspace (via `create` or `add-app`) and deployed as one unit, they
+already share one `.env`, one `A2A_SECRET`, and one workspace registry.
+Discovery and authenticated A2A calling both just work, with nothing to set
+up, whether that workspace is running on your machine or in production.
+This is the expected setup for a real multi-app product built on Calendar.
+
+### Separate deployments: one manual step
+
+If Calendar and Dispatch are two independently created Agent Native
+projects, they don't share a secret and can't call each other yet.
+Connecting them takes one manual step on each side: add a
+`remote-agents/<id>.json` resource with a shared secret, from Settings →
+Connected Agents, the Agent page's Connections tab, or Dispatch → Agents →
+Add external agent. See [A2A Protocol](/docs/a2a-protocol) for the full
+walkthrough.
+
+To check which situation you're in, ask either app's agent "what apps can
+you see?" If Calendar is missing from Dispatch's answer, you're in the
+second case.
+
+## Integration strategies
+
+**Automating off calendar events.** Creating an event and creating a booking
+both fire a real event on the shared framework event bus
+(`calendar.event.created`, `calendar.booking.created`). Any app's
+[automation](/docs/automations) can subscribe to either one, regardless of
+which app defines it. A booking landing on your calendar could trigger a
+welcome email draft in Mail, or a meeting agenda in Slides, built before the
+meeting happens. Calendar doesn't ship one of these automations out of the
+box, but the event is real and ready to hook into whenever you want to build
+one.
+
+**Natural-language delegation through Dispatch.** A sibling app doesn't need
+a special integration to work with Calendar. It can hand Calendar's agent a
+plain-English request, like "find 30 minutes with Sam next week," the same
+way you would in chat, and Calendar answers or acts on it directly. This is
+the real mechanism behind something like a scheduling request that arrives
+in Mail or Slack turning into a booked event: Dispatch (or the app that
+received the message) delegates the request to Calendar's agent, and
+Calendar handles it like any other prompt.
+
+**Staying decoupled.** Calendar never needs to know Mail's or Slack's
+credentials, or vice versa, for any of this. The event bus and the
+automations that subscribe to it sit between apps, so Calendar only has to
+emit a real event or answer a real request. It doesn't need to know who's
+listening, or how.
+
+## What's next
+
+- [**Calendar**](/docs/template-calendar) — the overview and getting-started steps
+- [**Features**](/docs/template-calendar-features) — views, availability, finding time, and booking links
+- [**Talk to the Agent**](/docs/template-calendar-agent) — prompts by task, application state, and Extensions
+- [**Developer Guide**](/docs/template-calendar-developers) — quick start, actions, data model, and routes
+- [**Dispatch**](/docs/template-dispatch) — the workspace control plane these patterns run under
+- [**Automations**](/docs/automations) — declaring an automation that reacts to a calendar event
+- [**A2A Protocol**](/docs/a2a-protocol) — how apps discover, authenticate with, and call each other
+- [**Multi-App Workspace**](/docs/multi-app-workspace) — the general pattern of composing first-party apps instead of nesting them

package/docs/content/template-calendar.mdx

@@ -1,135 +1,68 @@
 ---
 title: "Calendar"
-description: "An agent-powered calendar with Google Calendar sync and Calendly-style booking links. Schedule, find slots, and manage availability through plain English."
+description: "An agent-powered calendar that replaces Google Calendar and Calendly with one app you own. Schedule, manage availability, and handle booking links through the agent or the UI."
 ---
 
 # Calendar
 
-An agent-powered calendar app. Connect your Google Calendar and the agent can read your schedule, find free slots, create events, and manage Calendly-style booking links — all in plain English. It replaces the Google Calendar + Calendly combo with one app you own.
-
-<WireframeBlock id="doc-block-calendar1">
-  <Screen
-    surface="desktop"
-    html={
-      "<div style='display:flex;flex-direction:column;min-height:530px;box-sizing:border-box'><div style='display:flex;align-items:center;gap:10px;padding:14px 18px;border-bottom:1.4px solid var(--wf-line)'><button>Week</button><button>Today</button><button>‹</button><button>›</button><div style='flex:1'></div><strong>May 3-9, 2026</strong><div style='flex:1'></div><button class='primary'>New Event</button></div><div style='display:grid;grid-template-columns:56px repeat(7,minmax(0,1fr));grid-template-rows:36px repeat(5,72px);gap:7px;padding:14px;flex:1'><div></div><strong>Sun 3</strong><strong>Mon 4</strong><strong>Tue 5</strong><strong>Wed 6</strong><strong>Thu 7</strong><strong>Fri 8</strong><strong>Sat 9</strong><small class='wf-muted'>7 AM</small><div class='wf-box' style='opacity:.45'></div><div></div><div></div><div></div><div></div><div></div><div></div><small class='wf-muted'>9 AM</small><div class='wf-box'>All-hands</div><div class='wf-box'>Eng standup</div><div class='wf-box'>Eng standup</div><div class='wf-box'>Eng standup</div><div></div><div class='wf-box'>Planning</div><div></div><small class='wf-muted'>11 AM</small><div class='wf-box'>Design review</div><div></div><div class='wf-box'>Design crit</div><div class='wf-box'>Roadmap</div><div class='wf-box'>Friday demo</div><div></div><div></div><small class='wf-muted'>1 PM</small><div></div><div class='wf-box'>1:1</div><div class='wf-box'>Focus block</div><div></div><div></div><div class='wf-box'>All-hands</div><div></div><small class='wf-muted'>3 PM</small><div></div><div></div><div></div><div class='wf-box'>Skip-level</div><div></div><div></div><div></div></div></div>"
-    }
-  />
-</WireframeBlock>
-
-When you open the app, the active calendar view is the primary surface. The agent still knows which day, week, or event you're looking at, so you can say "schedule a 30-minute call with Alex on this day" without spelling everything out.
-
-<Diagram id="doc-block-calendar2" title="How a scheduling request flows" summary="Whether you click in the calendar or ask the agent, the same actions read live from Google Calendar and write back to the same view.">
-
-```html
-<div class="diagram-flow">
-  <div class="diagram-col">
-    <div class="diagram-node">
-      You click<br /><small class="diagram-muted"
-        >drag, toolbar, shortcuts</small
-      >
-    </div>
-    <div class="diagram-node">
-      You ask the agent<br /><small class="diagram-muted"
-        >"find a 1-hour slot next week"</small
-      >
-    </div>
-  </div>
-  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
-  <div class="diagram-panel center">
-    <span class="diagram-pill accent">Actions</span
-    ><small class="diagram-muted"
-      >list-events · check-availability · create-event</small
-    >
-  </div>
-  <div class="diagram-arrow diagram-muted" aria-hidden="true">&rarr;</div>
-  <div class="diagram-col">
-    <div class="diagram-box">
-      Google Calendar<br /><small class="diagram-muted"
-        >live, multi-account</small
-      >
-    </div>
-    <div class="diagram-box">
-      SQL<br /><small class="diagram-muted">bookings · availability</small>
-    </div>
-  </div>
-  <div class="diagram-arrow diagram-muted" aria-hidden="true">&#8635;</div>
-  <div class="diagram-box">Calendar view updates live</div>
-</div>
-```
-
-```css
-.diagram-flow {
-  display: flex;
-  align-items: center;
-  gap: 12px;
-  flex-wrap: wrap;
-}
-.diagram-flow .diagram-col {
-  display: flex;
-  flex-direction: column;
-  gap: 10px;
-}
-.diagram-flow .diagram-arrow {
-  font-size: 22px;
-  line-height: 1;
-}
-.diagram-flow .center {
-  display: flex;
-  flex-direction: column;
-  align-items: center;
-  gap: 4px;
-}
-```
-
-</Diagram>
-
-## What you can do with it
-
-- **See your real Google Calendar** in day, week, or month view, with multiple accounts overlayed in one grid.
-- **Subscribe to ICS feeds** (HR time off, conference schedules, team calendars) — read-only, mixed into the same view.
-- **Set weekly availability** with timezone support, buffer time, and minimum notice — the agent uses this when finding free slots.
-- **Create public booking links** at `/book/{your-name}/{slug}` for things like "15-minute intro" or "30-minute demo." Configure durations, custom fields, required co-hosts, and whether visitors get Google Meet or Zoom.
-- **Ask the agent anything schedule-related**: "Am I free Thursday afternoon?" "Find a 1-hour slot next week and put 'Planning with Alex' on it." "Pause my demo booking link."
-- **Share booking links** with teammates so they can manage them too.
-
-See [Scheduling, Availability & Finding Time](/docs/template-calendar-scheduling) and [Booking Links](/docs/template-calendar-booking-links) for the full detail on each.
-
-## Getting started
-
-Live demo: [calendar.agent-native.com](https://calendar.agent-native.com).
-
-When you first open the app:
-
-1. Click **Settings**.
-2. Click **Connect Google Calendar** and approve.
-3. (Optional) Connect more Google accounts if you want personal + work overlayed.
-4. Open the main view — your real calendar will load.
-
-To create your first booking link:
-
-1. Click **Booking Links** in the sidebar.
-2. Click **New booking link**, set a title and duration.
-3. Share the public URL — visitors pick from your available slots.
-
-Or just ask the agent: "Create a 15-minute intro booking link with a name field."
-
-### Useful prompts
-
-- "What is on my calendar today?"
-- "Am I free Thursday afternoon for 30 minutes?"
-- "Find a 1-hour slot next week and put 'Planning with Alex' on it."
-- "Create a booking link called '15 min intro' at 15 minutes with a note field."
-- "Block Friday afternoons on my availability."
-
-See [Talking to the Agent](/docs/template-calendar-agent) for the full list of prompts by task.
-
-The agent will query Google Calendar live for any schedule question — it never guesses.
+Calendar is an agent-powered scheduling app. Connect your Google Calendar and
+the agent can read your schedule, find free time, create events, and manage
+Calendly-style booking links, in plain English or with a click. It replaces
+the Google Calendar + Calendly combo with one app, so your real schedule and
+your public booking pages are never two things you have to keep in sync by
+hand.
+
+<Cards columns={1}>
+
+### :calendar: [Try it out now →](https://calendar.agent-native.com)
+
+See Calendar live with a real Google Calendar connected.
+
+</Cards>
+
+<Video
+  src="https://cdn.builder.io/o/assets%2FYJIGb4i01jvw0SRdL5Bt%2Fafb81b5670d44030960cf8b60ec77c53?alt=media&token=59a6171c-f074-4507-91fe-db820cbe007e&apiKey=YJIGb4i01jvw0SRdL5Bt"
+  alt="A short screen recording of logging in and touring the calendar app."
+  caption="A brief tour of the calendar application."
+  autoplay={true}
+  loop={true}
+/>
+
+## What it replaces
+
+<Comparison>
+
+### Before
+
+- Google Calendar for your real schedule
+- Calendly (or similar) for public booking links, kept in sync by hand
+- A separate contacts search when you need someone's email
+- Copy-pasting a Zoom link into every invite
+
+### After
+
+- One view: your real calendar and your booking links together
+- One availability model that booking links and the agent both read from
+- People search built into the same prompt as scheduling
+- Zoom or Google Meet attached automatically when someone books
+
+</Comparison>
+
+## Calendar in a multi-app workspace
+
+If you're running Calendar alongside other apps under
+[Dispatch](/docs/template-dispatch), your calendar stops being just a page you
+open. It becomes something other channels and apps can act on, from
+automations that fire off a new booking to a sibling app handing Calendar a
+scheduling request directly. See [Calendar in a Multi-App
+Workspace](/docs/template-calendar-integrations) for how the connection
+actually works and the real mechanisms behind it.
 
 ## What's next
 
-- [**Scheduling, Availability & Finding Time**](/docs/template-calendar-scheduling) — views, availability, free-slot search, overlays, and people search
-- [**Booking Links**](/docs/template-calendar-booking-links) — creating, sharing, and managing Calendly-style booking pages
-- [**Talking to the Agent**](/docs/template-calendar-agent) — prompts by task, application state, and Extensions
+- [**Features**](/docs/template-calendar-features) — views, availability, finding time, and booking links, with setup steps for each
+- [**Talk to the Agent**](/docs/template-calendar-agent) — prompts by task, application state, and Extensions
+- [**Calendar in a Multi-App Workspace**](/docs/template-calendar-integrations) — integration strategies and connecting to Dispatch
 - [**Developer Guide**](/docs/template-calendar-developers) — quick start, actions, data model, and routes
 - [**Templates**](/docs/cloneable-saas) — the Cloneable SaaS model, and every other domain template to start from
 - [**Getting Started**](/docs/getting-started) — the framework fundamentals: actions, application state, and live sync

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.172.3",
+  "version": "0.172.6",
   "description": "Framework for agent-native application development — where AI agents and UI share SQL state, actions, and context",
   "homepage": "https://github.com/BuilderIO/agent-native#readme",
   "bugs": {

package/docs/content/template-calendar-booking-links.mdx

@@ -1,73 +0,0 @@
----
-title: "Calendar: Booking Links"
-description: "Create Calendly-style public booking pages, connect Zoom or Google Meet, and manage bookings people make with you."
----
-
-# Booking Links
-
-Booking links are public pages where anyone can pick a time and book it directly onto your calendar — the Calendly-style part of Calendar. This page covers creating, sharing, and managing them. See [Calendar](/docs/template-calendar) for the overview and [Events, Availability & Finding Time](/docs/template-calendar-scheduling) for the availability rules booking links use.
-
-## Creating a booking link
-
-A booking link needs a title and a duration (like "15 min intro" at 15 minutes). From there you can add:
-
-- **Alternate durations** so a visitor can choose 15, 30, or 60 minutes on the same link
-- **Custom fields** to collect a company name, a topic, or anything else before the meeting
-- **A conferencing choice** — Google Meet, Zoom (once connected — see below), or a custom link
-- **A color** so the link's bookings stand out on your calendar
-- **Required co-hosts** — other people who must also be free before a slot is offered. When someone books, everyone (you and your co-hosts) gets invited to the resulting Google Calendar event.
-
-Ask the agent to create one ("Create a 15-minute intro link with a name and company field") or use **New booking link** in the sidebar.
-
-## Connecting Zoom or Google Meet
-
-Booking links can generate a real video meeting automatically when someone books:
-
-- **Google Meet** needs no setup — it's added the same way any Google Calendar invite gets a Meet link.
-- **Zoom** needs your Zoom account connected first. Connect it once from Settings; after that, any booking link set to Zoom creates a real Zoom meeting for each new booking and attaches the join link to the confirmation.
-
-If Zoom isn't connected yet and a link is set to use it, ask the agent to help you connect it, or do it from Settings directly.
-
-## Sharing a booking link with teammates
-
-Sharing controls who can _manage_ the link — edit its duration, pause it, or see its bookings — through the standard viewer/editor/admin roles. It's separate from public access: anyone with the URL can still book as long as the link is active, whether or not they have management access.
-
-## The public booking page
-
-Every booking link has a public URL at `/book/{your-booking-name}/{slug}` — for example `/book/steve/30min`. Your booking name is generated automatically from your email the first time you create a link, and you can change it later from Settings (up to three times every 30 days, since it's part of every public link you've shared).
-
-A visitor picks an available time from your real availability, fills in their name, email, and any custom fields you added, then confirms. They get a confirmation with a link to manage their own booking.
-
-<WireframeBlock id="doc-block-calendar4">
-  <Screen
-    surface="desktop"
-    html={
-      "<div style='display:flex;flex-direction:column;min-height:480px;box-sizing:border-box;padding:36px 60px;gap:16px'><h2 style='margin:0'>30 min with Steve</h2><p class='wf-muted' style='margin:0'>Quick intro call — tell me a bit about what you're working on.</p><div style='display:flex;gap:20px;flex:1'><div class='wf-card' style='flex:1;display:flex;flex-direction:column;gap:8px'><strong>May 2026</strong><div style='display:grid;grid-template-columns:repeat(7,1fr);gap:6px'><span class='wf-muted'>Su</span><span class='wf-muted'>Mo</span><span class='wf-muted'>Tu</span><span class='wf-muted'>We</span><span class='wf-muted'>Th</span><span class='wf-muted'>Fr</span><span class='wf-muted'>Sa</span><span></span><span></span><span></span><span></span><span></span><span class='wf-pill accent'>1</span><span></span><span></span><span></span><span></span><span></span><span></span><span></span><span></span></div></div><div class='wf-card' style='flex:1;display:flex;flex-direction:column;gap:8px'><strong>Friday, May 1</strong><button>9:00 AM</button><button>9:30 AM</button><button class='primary'>10:00 AM</button><button>10:30 AM</button><button>2:00 PM</button></div></div></div>"
-    }
-  />
-</WireframeBlock>
-
-## Managing, rescheduling, or cancelling a booking
-
-Every confirmation includes a private manage link. Visitors use it to reschedule to a different open slot or cancel outright, without needing an account — no sign-in, since the link itself is the credential. You (the host) see all bookings, past and upcoming, in the **Bookings** list.
-
-## Renaming a link
-
-You can change a booking link's URL slug at any time — for example from `/book/steve/into-call` to `/book/steve/intro`. The old URL keeps working: visitors who still have the old link are automatically forwarded to the new one, so nothing you've already shared (an email signature, a website) breaks.
-
-### Useful prompts
-
-- "Create a 15-minute intro booking link with a name and company field."
-- "Add Brent as a required co-host on my 'Steve + Brent' link."
-- "Switch my '30 min demo' link to Zoom."
-- "Pause my '30 min demo' booking link."
-- "Rename my intro link's URL to '/intro'."
-- "Show me this week's bookings."
-
-## What's next
-
-- [**Calendar**](/docs/template-calendar) — the overview and getting-started steps
-- [**Events, Availability & Finding Time**](/docs/template-calendar-scheduling) — the availability rules booking links draw from
-- [**Talking to the Agent**](/docs/template-calendar-agent) — group/co-host links and more prompts
-- [**Developer Guide**](/docs/template-calendar-developers) — the booking data model and actions
-- [**Sharing**](/docs/sharing) — the share-grant model booking links build on