# Move or add a meeting from a chat message

> Move or add a meeting from a chat message: 2 companies fully do it, 22 with a limit, 45 carry the tag. Every listing in Personal assistants with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/personal-assistants.calendar-change/
- Markdown: https://www.anchorterminal.com/niches/personal-assistants.calendar-change/index.md (~2,600 tokens)
- Slim: https://www.anchorterminal.com/niches/personal-assistants.calendar-change/index.min.md (~530 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/personal-assistants.calendar-change/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 22 | 45 | 10 | 5 |

## What counts as done

The event exists or is moved on the connected calendar with the right date, time and attendees, confirmed back in the chat. Where the change notifies other people, the assistant asks first unless the owner has allowed it.

Measured, for our own tests: the change is made and confirmed in one exchange.

How agents ask for it: move my 3pm to Thursday; add these dates to the family calendar; when am I free next week; schedule a call with X

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Brea (Brea AI LLC)**: Inviting someone or accepting an invitation is on the approval list; Google Calendar and Microsoft Outlook Calendar are connectors; small changes to your own things run without asking.
- **Caddy (Caddy Technologies Inc.)**: Checks a connected Google Calendar, shows the time and guests, and an invitation with external attendees requires review; changes to your own calendar run on request.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Boba (humans& ai, inc.)**: Puts plans on the calendar and sends group invites to everyone; no approval statement covers invites.
- **Claude Duet (Anthropic, PBC)**: Google Calendar is a connector and messages need approval, but invites are not named among gated actions and Microsoft 365 is not available yet.
- **folk (Nozomio, Inc.)**: Google Calendar connects and anything that books or shares waits for an ok, but no calendar write or invite example is documented.
- **GAIA (The Experience Company, Inc.)**: Google Calendar is an integration and chat chains calendar and email actions, but with the always_allow default an invite goes out unprompted.
- **Gemini Spark (Google LLC)**: Schedules, moves and cancels events and asks before sending communications, but bulk actions on private Google Tasks run without confirmation.
- **Hermes Agent (Nous Research, Inc.)**: calendar create runs through the skill with no prompt before an invite; OAuth is a paste-back of the redirect URL, which works without a local browser.
- **IronClaw (Jasnah, Inc. d/b/a NEAR AI)**: A Calendar extension exists and OAuth uses a redirect URI on the instance host, but the auto-approve default lets an invite go without a prompt.
- **Lindy (Crivello Corp (doing business as Lindy))**: Smart scheduling sends invites from Google or Microsoft calendars, but the approval guardrail covers shared Slack threads only.
- **Lobby (Lobby OS, Inc.)**: Scheduling coordination is listed among prepared workflows with approval first; vendor claim with no documentation of calendar writes.
- **Dots (OpenAI)**: A new recipient on any route needs fresh authorisation and connected-app writes pass Auto-review, but no calendar plugin was named in the pages read, only Gmail, Drive and GitHub.
- **OpenClaw (OpenClaw Foundation)**: No first-party calendar connector in the docs read; owners add Google Calendar through skills and report it working from Telegram (acc-38, acc-39). Invites go out with no prompt and headless Google OAuth broke for acc-02.
- **OpenInstinct (Merit Systems, Inc.)**: Calendar events with attendees send Google invitations, and the approval step for calendar actions was removed on 2 October 2026.
- **Orbits (Nemus AI, Inc.)**: Household chat creates and updates events on synced iCloud, Google and Outlook calendars with proposed changes shown for approval before they apply; vendor claim only.
- **Orchid (Zero Email, Inc.)**: Calendar holds wait for the owner's okay on Google Calendar, per the safety post; no other provider and no documentation beyond the vendor's word.
- **Pally (Pally Technologies, Inc.)**: Google, Outlook and iCloud calendars connect and the same approval rule covers sends; the changelog records meeting prep and calendar reads, with no first-hand account of invites.
- **Poke (The Interaction Company of California Inc.)**: Creates and manages calendar events, including recurring ones, on Google and Outlook; nothing documents a prompt before invites reach attendees, and release notes record wrong attendees and times.
- **Skydive (Create, Inc.)**: Google Calendar and Outlook Calendar integrations exist; approval before an invite is a persona instruction, not a setting.
- **Tab (Terrasoft, Inc.)**: A home page example drafts an email to move a meeting, sends it after approval and moves the invite; vendor example only, private beta behind a waitlist.
- **Tomo (Mapo Labs, Inc.)**: Managing your calendar is claimed on the about page with no detail on writes, invites or approval.
- **Town (Town.com, Inc.)**: Calendar invites create approval requests in Human in the Loop mode across Google and Microsoft 365 calendars, but the Auto default lets a requested change go out without a further prompt.
- **Zapia (Brainlogic AI SAS)**: Organises your calendar and schedules messages per the home page and reviews; no detail on invites or approval.
- **Zo Computer (Zo Computer Company)**: Google Calendar and Outlook Calendar tools exist, with no documented prompt before an invite reaches attendees.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Boski (Boski, Inc.)**: Meeting prep is shown; no calendar write or invite example on the pages read.
- **Grok Bot (Anysphere, Inc.)**: No calendar connector appears in the pages read, though approvals would cover an invite.
- **Hark Pro (Hark Labs, Inc.)**: hark.com's robots.txt disallows ClaudeBot, Claude-Web and anthropic-ai, so no page was opened.
- **Haven (Hello Haven, Inc.)**: Manage your calendar is claimed; no provider, write flow or confirmation is described.
- **Instinct (Spear Street Technology, Inc. (d/b/a Instinct))**: No calendar provider or flow on the pages read.
- **Natura tinyNature (Natura Inc.)**: Calendars are shared read-only in the copy; nothing describes creating or moving events.
- **OpenDuet (Tawkit, Inc. (d/b/a CopilotKit))**: The README says it reads today's calendar; whether the Google connector writes events or sends invites is not stated.
- **Tasker AI (DAPI, Inc. (dba Tasker AI))**: No documentation found.
- **Wajo (Fo) (Wajo, Inc.)**: The platform lists calendar among system tools, but nothing documents how Fo changes an owner's calendar or whether it asks first.
- **ZeroClaw (ZeroClaw Labs)**: The google_workspace tool the listing names was not opened, so calendar writes and their risk class could not be read.

- not this job: AI Job Search (Mads Lorentzen): No calendar connector or command in the README.
- not this job: asaply (Asaply Inc.): Reservations and pickups, not calendar events; no calendar named.
- not this job: Asmi (Humint Labs, Inc.): Books appointments with businesses by phone; no calendar connector.
- not this job: AstrBot (AstrBotDevs): No calendar connector; an MCP calendar tool would run without a prompt.
- not this job: Atticus (An individual developer (GitHub SaarthurR)): Requests come from a shortcut or typing box on the Mac, not a chat message; no calendar connector.
- not this job: CowAgent (zhayujie): No calendar connector and no approval gate for an MCP calendar tool.
- not this job: DeepTutor (HKUDS): No calendar tooling.
- not this job: Del (Human Interface, Inc.): Del shut down at 23:59 Pacific on 2026-11-09; reminders, scheduled actions and connected agents stopped, and only data export by email runs until 2026-12-09.
- not this job: HireAlpha (HireAlpha): Calendar access is read-only (calendar.read); no write or invite is documented.
- not this job: LearnHarness (No legal entity found. Copyright Amos Blomqvist): No calendar.
- not this job: Leon (No legal entity found. Copyright Louis Grenard): No calendar connector.
- not this job: nanobot (HKUDS): No calendar tool or connector; a calendar needs an owner-added MCP server, and nothing asks before a write.
- not this job: NanoClaw (NanoCo, Inc.): No calendar connector or skill; the owner would register an MCP server and configure credential approval themselves.
- not this job: Octop (Tencent Cloud): No calendar connector; Tencent Meeting is the nearest and is not a calendar.
- not this job: PicoClaw (Sipeed): No calendar tool or connector; MCP servers only, with no approval before writes.
- not this job: QwenPaw (Qwenpaw PRIVATE LIMITED): No calendar tool or connector in the docs; only MCP servers the owner adds.
- not this job: szn (Nomadic Futures, Inc.): Scheduling an appointment with a business is an errand; no owner-calendar write is described.
- not this job: Talorys (Roc Yu (rociiu) and contributors): No calendar connection.

## What stops agents finishing

- calendar invites go to other people, and several tools send them without a prompt (Caddy's example adds an event directly; Gemini runs bulk Tasks changes unasked)
- Google OAuth needs a browser the headless server doesn't have

## Around it

Before: personal-assistants.inbox-triage-draft, ocr.screenshot-to-text. After: calendar.write, email.send.

## Where this comes from

Weight 10 of 100 in Personal assistants: 5 of 40 accounts (acc-02, acc-19, acc-38, acc-39, acc-41) and the shared task suite's meeting-to-move; fewer first-hand stories than mail because it mostly works and people don't write about it.

As data: https://www.anchorterminal.com/api/v1/use-cases/personal-assistants.calendar-change.json, or the MCP tool get_use_case with id personal-assistants.calendar-change. Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
