# Agentic Scheduling = Apple Calendar + Apple Reminders + Claude Agent > Source: > Published: 2026-08-13 22:00:59+00:00 **Your calendar, run by an AI agent you can text.** A self-hostable, single-owner scheduling platform. It syncs your Google and Outlook calendars, gives visitors a booking page that shows only your open slots, and puts a Claude agent in charge, controllable from the web or WhatsApp. *Demo: a visitor asks the assistant for open times, then the Chrome extension overlays your own free/busy on someone else's Calendly page. ( full-quality video)* *The public booking page. Visitors pick a length and a day.* *Picking a day opens the open times. Every slot shown is genuinely free across all connected calendars.* *The same page, agent mode. Visitors ask in plain language and the assistant answers from live availability. It can also book the chosen slot.* *The Chrome extension on someone else's Calendly page (Calendly's public demo). Every slot is badged with your own free/busy, pulled live from your deployment, so you never book yourself into a conflict.* *The same booking flow on a phone.* *Reminders on both channels. Left: the confirmation and reminder email an attendee receives. Right: the WhatsApp messages the owner receives, a booking alert the moment someone books and a reminder before the meeting. Rendered from the real templates with sample data.* Connect any number of Google and Outlook accounts (seven calendars, one place). The availability engine merges their free/busy into one view, the booking page offers only real openings, and confirmed bookings are written back to the calendar you choose. ``` %%{init: {"themeVariables": {"fontSize": "12px"}}}%% flowchart TB subgraph cal["Your calendars, any number"] direction LR G1["Google 1"] G2["Google 2"] G3["Google N"] O1["Outlook 1"] O2["Outlook N"] end cal --> AGG["Free/busy aggregation
merged in UTC"] AGG --> AV["Availability engine
open slots, revalidated at booking time"] AV --> BP["Public booking page"] AV --> AG["Claude agent"] AG --> WA["WhatsApp
control, alerts, reminders"] AG --> EM["Email
confirmations, reminders"] BP --> DEST["Destination calendar
event and invite written back"] ``` **Calendar sync across providers.** Aggregates free/busy from any number of Google and Microsoft (Outlook) accounts, each connected by OAuth. Bookings are written to the calendar you designate.**A booking page that only offers real openings.** An agent continuously checks your merged calendars for open slots. Availability is revalidated at booking time, so a slot that was just taken cannot be double-booked.**WhatsApp direct communication.** Text the agent to create, move, or cancel events, check availability, or set reminders. New bookings, cancellations, and reschedules are pushed to you on WhatsApp and email the moment they happen.**Reminder emails and WhatsApp reminders.** Attendees and the owner get meeting reminders over email and approved WhatsApp templates. A claim/dead-letter worker retries failed sends instead of dropping them.**Ask-the-assistant on the booking page.** Visitors can chat with a public agent to find a time. It is handed exactly two scope-fenced tools. The private tools are never constructed for it, so safety comes from architecture, not from prompts.**Daily morning brief.** A DST-safe WhatsApp summary of the day's meetings and tasks.**Self-serve reschedule and cancel.** Every confirmation carries a signed link the attendee can use without an account.**Chrome extension.** Overlays your real availability on other people's Calendly pages. Booking, agents, reminders, and calendar extras (personal blocks, birthdays, follow-ups) are plain JSON APIs under `src/app/api/` , so you can reuse them from any client. **Agent-to-agent scheduling.** A visitor's agent and your agent negotiate a meeting time over a shared protocol and book the result. ``` git clone https://github.com/hunterZh37/agentic-scheduling.git && cd agentic-scheduling npm install cp .env.example .env # defaults work out of the box docker compose up -d # local Postgres npx prisma migrate dev && npx prisma db seed npm run dev # http://localhost:3000 ``` The app boots fully on placeholder config, so you can click through the UI before connecting anything real. When you are ready to go live, [docs/SETUP.md](/hunterZh37/agentic-scheduling/blob/main/docs/SETUP.md) walks through each credential (Google, Microsoft, Anthropic, Twilio, Resend) one at a time, in any order. All identity comes from environment variables: owner name, email, timezone, phone numbers, and calendar credentials (see [ .env.example](/hunterZh37/agentic-scheduling/blob/main/.env.example)). The one file with brand defaults baked in is [(practice name, domain, consulting areas, research link). Edit it when deploying your own instance.](/hunterZh37/agentic-scheduling/blob/main/src/lib/booking/publicConfig.ts) `src/lib/booking/publicConfig.ts` Everything is environment variables (see [ .env.example](/hunterZh37/agentic-scheduling/blob/main/.env.example)). No personal data is hardcoded. [docs/SETUP.md](/hunterZh37/agentic-scheduling/blob/main/docs/SETUP.md): credentials, mapped to each env var[docs/DEPLOY.md](/hunterZh37/agentic-scheduling/blob/main/docs/DEPLOY.md): deploying to Vercel[docs/SMS.md](/hunterZh37/agentic-scheduling/blob/main/docs/SMS.md): the WhatsApp/SMS control channel[docs/MORNING_BRIEF.md](/hunterZh37/agentic-scheduling/blob/main/docs/MORNING_BRIEF.md): the daily WhatsApp brief Next.js (App Router), React 19, and TypeScript on Vercel. Postgres via Prisma. Claude tool-calling for the agents. Twilio for SMS/WhatsApp, Resend for email, VAPID for web push. Luxon and rrule for time and recurrence. Vitest for tests. Issues and PRs welcome. Run `npm test` and `npm run lint` before submitting. [MIT](/hunterZh37/agentic-scheduling/blob/main/LICENSE) © Ze Dong (Hunter) Zhang