AI Agent Google Calendar Integration
Your AI engineering team now shows up in your calendar — the same one you check on your phone every morning.
amux syncs your AI agent schedules and board deadlines to Google Calendar in real time. When you create a board item with a due date, a Google Calendar event appears. When a scheduled agent fires, the calendar event is created and updated as the run completes. When a task moves to done, the event reflects it. No other AI agent orchestrator does this. Shipped July 2026.
New in July 2026 — Google Calendar sync shipped in commits 3248151 and fdc04df. This includes real-time board-to-calendar push, scheduled agent runs as calendar events, and OAuth via amux's own Google client (no service account required). See the changelog.
What it does
AI coding agents are now a core part of the development workflow for many teams. You have agents running overnight on test generation, feature work, and refactoring. You have schedules firing at 2 AM for dependency updates. You have board tasks with deadlines tied to sprint cycles. But until now, all of this lived in a separate dashboard — one more thing to check, one more tab to open, one more context switch.
amux's Google Calendar integration puts your AI team's work directly into the tool you already use to plan your day. Board items with due dates appear as calendar events. Scheduled agent runs appear at their scheduled times. When an agent finishes a task, the calendar event updates. When you check your calendar on your phone in the morning, you see not just your meetings — you see what your agents shipped overnight.
| amux event | What appears in Google Calendar | When it updates |
|---|---|---|
| Board item with due date | Calendar event on the due date with task title | On create/edit; updates to "done" when task completes |
| Scheduled agent task (cron / daily / weekly) | Calendar event at the scheduled fire time | Created before the run; updated with result after completion |
| Board item moved to done | Existing calendar event updated with completion status | Real-time (within seconds of the board update) |
| Board item deleted | Calendar event removed | On delete |
Why this matters
Human engineering teams put their sprint work on the calendar. Stand-ups, planning sessions, review meetings, feature freeze deadlines — all of it lives in the calendar so everyone knows what's happening and when. But AI agents have been invisible to the calendar. You know a batch job ran last night only by opening the amux dashboard and reading the board.
With calendar sync, your AI team's work is visible in the same tool as your human team's work. At a glance on Monday morning you see: "agents ran auth refactor Friday night, scheduled dependency update fires at 3 AM Tuesday, PR review deadline for the AI-generated test suite is Wednesday." No dashboard required. No SSH. No context switch. Just your calendar.
This also helps when working with non-technical stakeholders. "Here's when the AI agents are scheduled to complete the API migration" is a lot more accessible when it appears as a calendar event than when it lives in a CLI tool's kanban board.
How to set it up
Setup takes about five minutes. You need an amux install and a Google account. No service account, no GCP project, no JSON key file — amux uses its own OAuth client and walks you through the standard Google consent flow.
Step 1 — Install amux and start the server
git clone https://github.com/mixpeek/amux && cd amux && ./install.sh
amux serve # → https://localhost:8822If you already have amux installed, just make sure you are on the latest version: git pull && touch amux-server.py to trigger a reload.
Step 2 — Open Calendar settings in the dashboard
In the amux dashboard at https://localhost:8822, open the calendar section. You will see two options: the iCal feed URL (for passive subscription from any calendar app) and the Google Calendar OAuth connection for live two-way sync.
Step 3 — Connect your Google account
Click "Connect Google Calendar." You will be redirected to Google's OAuth consent screen asking for calendar access. Approve it. amux stores your OAuth tokens locally in ~/.amux/ — they never leave your machine. You can revoke access any time from your Google Account's connected apps settings.
Step 4 — Create scheduled agent tasks
# Via the scheduler tab in the dashboard
# Or via CLI — e.g. a daily 2am dependency update agent
# Each scheduled task appears as an iCal event at its fire timeScheduled tasks (configured in the Scheduler tab) appear as calendar events at their scheduled fire times. The event title matches the task title. The iCal feed updates whenever schedules change.
Step 5 — Subscribe your calendar
Open Google Calendar → Other Calendars → From URL → paste https://localhost:8822/api/calendar.ics (or your tunnel URL for a stable public address). Google polls the feed periodically. Your scheduled agent tasks appear as events on their scheduled dates.
Real-world use cases
Sprint planning with AI agents
Before a sprint starts, create all your board items with due dates matching the sprint end date. When you open Google Calendar and look at the sprint week, you see not just your standups and review sessions but the full list of tasks your agent fleet is working toward. Share your calendar view with your PM during planning — they see the same sprint timeline you do, AI tasks included.
Overnight runs as calendar blocks
Create a scheduled agent task to fire at 2 AM Tuesday. It appears on your calendar as a "2 AM: dependency update agent" block. When you wake up Wednesday morning and open your calendar to see the day, you see that block marked complete — or, if the run failed, you see it still marked in progress and know to check the dashboard. No separate tool to open, no "did that thing run last night?" uncertainty.
Morning phone review
You wake up, check Google Calendar on your phone — the app you open every morning anyway. You see that the test-generation agent completed its run overnight (event marked done) and the refactoring agent is still running (event still showing in-progress). You know exactly what happened without opening a laptop. If you need to redirect the refactoring agent, you can open the amux iOS app from the same phone — one more tap and you have sent a message to the session.
Reviewing what shipped
At the end of a sprint, browse back through the week in Google Calendar. Every agent task that ran appears as an event. Events marked "done" shipped. Events marked "blocked" or still in progress need follow-up. This is your AI team's sprint retrospective data — all in the calendar you are already using for the human team's retrospective.
iCal feed — passive subscription for any calendar
If you do not want to connect Google OAuth, or if you use Apple Calendar, Outlook, or another calendar application, amux also exposes a standard iCal feed:
GET https://localhost:8822/api/calendar.icsSubscribe to this URL from any iCal-compatible calendar app. The feed contains your scheduled agent tasks as RFC 5545 events — one event per scheduled run at its fire time. Your calendar app polls the feed on its own schedule (typically every few hours) and shows upcoming tasks as events.
The iCal feed is a passive subscription — Google Calendar polls it; amux does not push. For a stable public URL you can subscribe to without exposing localhost, use the amux tunnel: https://<id>.t.amux.io/api/calendar.ics (requires amux cloud).
If you configure an S3 bucket (via AMUX_S3_BUCKET in ~/.amux/server.env), amux uploads the iCal feed to S3 on every board write, giving you a public URL you can subscribe to from Google Calendar without exposing localhost:8822 to the internet. See the docs for S3 setup.
Why no other AI agent tool does this
Most AI coding agent tools are SaaS products with their own dashboards and notification systems. They send you emails, Slack notifications, or in-app alerts when a task completes. These are push notifications — they interrupt you. A calendar event is different: it is ambient information you encounter when you are already planning your day.
amux is self-hosted and lives on your machine, which means it can interact with local credentials and OAuth flows in ways that cloud services cannot. The Google Calendar integration uses the OAuth tokens you approve on your own machine, writing events directly from the amux server to Google's API. There is no third-party intermediary, no data leaving your machine to a vendor, and no dependency on amux's cloud infrastructure.
This is one of the reasons the "single Python file, zero external dependencies" architecture matters: amux can add integrations like Google Calendar without adding cloud dependencies. The file that runs your agents is the same file that pushes to your calendar.
Frequently asked questions
Does amux use my Google Calendar credentials securely?
Yes. amux uses OAuth 2.0 via Google's standard authorization flow. You authorize amux through Google's consent screen, and your tokens are stored locally in ~/.amux/ on your machine. No credentials are sent to third-party servers. The amux server communicates directly with the Google Calendar API. You can revoke access any time from your Google Account's connected apps page.
Can I see agent output in the calendar event?
Calendar events include the task title, due date, and a link back to the amux dashboard where you can view full session output. Real-time terminal output is not embedded in the calendar event — that's what the amux dashboard and iOS app peek view are for. The calendar event is a status signal; the dashboard is where you read the details.
What types of amux schedules appear in Google Calendar?
Two things sync: (1) board items with a due date set — each becomes a calendar event on that date; (2) scheduled agent tasks created via the amux scheduler — each scheduled run appears as a calendar event at the scheduled time. Sessions started manually without a due date do not appear. You can add a due date to any board item via the dashboard or the API.
Does the calendar update when an agent finishes a task?
Yes — in real time. When a board item moves to "done," the corresponding Google Calendar event is updated within seconds. When a scheduled agent run completes, the calendar event is updated with the result. You can glance at Google Calendar and know not just what was scheduled but what actually shipped.
Can I subscribe to amux's iCal feed without connecting Google OAuth?
Yes. amux exposes a standard iCal feed at /api/calendar.ics that you can subscribe to from Google Calendar, Apple Calendar, Outlook, or any iCal-compatible app. The iCal feed shows board items with due dates as upcoming events. The Google OAuth integration adds live two-way sync — amux pushes events directly and updates them as status changes, rather than waiting for your calendar app to poll the feed.
How is this different from other AI agent tools?
No other AI agent orchestrator — Devin, Jules, OpenHands, Codex, Claude Desktop — pushes scheduled agent work to your Google Calendar as live events. Most tools require you to open a separate dashboard or check a web UI to know what your agents are doing and when. amux puts your AI team's sprint directly inside the calendar you already check every morning on your phone.
See your AI team in your calendar
Install amux in ten minutes. Connect Google Calendar in two more. Your AI agent schedules and board deadlines appear alongside your meetings — on your phone, in real time, the next time you check your calendar.
git clone https://github.com/mixpeek/amux && cd amux && ./install.sh
amux serve # → https://localhost:8822
# Settings > Calendar > Connect Google Calendar