Skip to content

armgit / macro

Public Imported from GitHub
0

Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.

fix: enable calendar scheduling by default in dev (#7437)

teoacf5b2033663
diff --git a/apps/web/src/lib/core/constant/featureFlags.ts b/apps/web/src/lib/core/constant/featureFlags.ts
index 4e0fe9036f..d689db30e2 100644
--- a/apps/web/src/lib/core/constant/featureFlags.ts
+++ b/apps/web/src/lib/core/constant/featureFlags.ts
@@ -597,10 +597,11 @@ export function isCalendarSearchUiEnabled(): boolean {
}
// Scheduling settings, calendar shortcuts, and public booking/receipt pages.
-// Off until PostHog enables it, including in dev.
+// On in dev; production defers to PostHog.
export const enableCalendarScheduling = defineFlag({
key: 'enable-calendar-scheduling',
env: 'ENABLE_CALENDAR_SCHEDULING',
+ default: onInDev,
});
// The "Enable calendar" prompt on phones. Off by default everywhere,
diff --git a/docs/AGENT_GUIDE/surfaces.md b/docs/AGENT_GUIDE/surfaces.md
index 3dc84a86bd..b713a4bd0a 100644
--- a/docs/AGENT_GUIDE/surfaces.md
+++ b/docs/AGENT_GUIDE/surfaces.md
@@ -1120,12 +1120,13 @@ footer. Answering a recurring invitation opens a rounded glass sheet: choose
`This event` or `All events`, then `Save response`. Cancel or Close returns to
the event details without sending a response.
-Calendar scheduling requires the PostHog flag `enable-calendar-scheduling`, which
-is off unless enabled remotely (including in dev). For local browser checks,
-`VITE_ENABLE_CALENDAR_SCHEDULING=true` overrides it. While off, the Calendar settings
-tab and calendar booking shortcuts are hidden; public booking and receipt links
-show an unavailable page without fetching scheduling data. When enabling a hosted
-rollout, include anonymous visitors so invitees can open those links.
+Calendar scheduling is on by default in dev. Production uses the PostHog flag
+`enable-calendar-scheduling` and stays off unless enabled remotely. Set
+`VITE_ENABLE_CALENDAR_SCHEDULING=false` to test the disabled state locally.
+While off, the Calendar settings tab and calendar booking shortcuts are hidden;
+public booking and receipt links show an unavailable page without fetching
+scheduling data. When enabling a production rollout, include anonymous visitors
+so invitees can open those links.
When enabled, calendar scheduling lives in **Settings → Calendar** (`/app/settings/calendar`).
The scheduling sidebar opens Event types, Bookings, Availability, Teams, Insights,
diff --git a/docs/CALENDAR_SCHEDULING_V1.md b/docs/CALENDAR_SCHEDULING_V1.md
index 4a95a7ba7e..666cfe4962 100644
--- a/docs/CALENDAR_SCHEDULING_V1.md
+++ b/docs/CALENDAR_SCHEDULING_V1.md
@@ -79,12 +79,13 @@ tests do not verify real invitations, OAuth, or Meet creation.
- Apply `20260918164303_calendar_scheduling.sql`, then `20260918175703_scheduling_recovery.sql`
before deploying the calendar service. Both are additive; the second adds a nullable retry
timestamp, partial recovery index, and bounded per-profile request budgets.
-- Leave the frontend PostHog flag `enable-calendar-scheduling` disabled until the
- connected-account checks below pass. An absent flag is also off, including in dev;
- `VITE_ENABLE_CALENDAR_SCHEDULING=true` is available for local testing. The flag gates
- the Calendar settings tab, calendar booking shortcuts, and public booking/receipt pages
- before their queries mount. Hosted rollout targeting must include anonymous visitors
- so invitees can book and manage bookings. Disabling it also hides existing receipt links.
+- Leave the production PostHog flag `enable-calendar-scheduling` disabled until the
+ connected-account checks below pass. An absent flag is also off in production.
+ Scheduling is on by default in dev; set `VITE_ENABLE_CALENDAR_SCHEDULING=false`
+ to test the disabled state locally. The flag gates the Calendar settings tab,
+ calendar booking shortcuts, and public booking/receipt pages before their queries mount.
+ Production rollout targeting must include anonymous visitors so invitees can book and
+ manage bookings. Disabling it also hides existing receipt links.
This frontend flag does not disable backend routes, recovery, or migrations.
- Keep the existing `CALENDAR_SYNC_ENABLED` switch enabled for scheduling routes and recovery.
New configuration cannot turn on manual approval. Automatic provider invitations remain active.