Limitations and roadmap
Honest caveats about what the Agent API can and cannot do today, and what is planned but not yet shipped.
The Agent API is powerful but young. Before you wire up automation, read this page. It lists the known limitations you should plan around today, plus what is on the roadmap but not yet shipped. Every other page in these docs assumes you have read this one.
Known limitations
Disconnecting is silent, and uninstalling does not remove webhooks
Revoking a pairing now removes that client's token and its webhooks in one atomic step. But the disconnected client is not notified, its next call just returns 401. Uninstalling an MCP client revokes its token and deletes its token file, but it does not delete any webhooks that client created; remove those separately.
Connecting an assistant grants recording control
A per-client token's baseline scope includes record, not just read. A connected assistant can start and stop recording, not only read past meetings. The consent_attested field on the recording-start call is accepted by the API today, but it currently has no effect on behavior.
Paired tokens expire; loopback and MCP tokens do not
A token issued to a paired LAN client expires 90 days after it is minted. The same-machine loopback token and the per-client MCP tokens do not auto-expire.
Webhook management is limited
You can create, test, and delete webhooks over the HTTP API and the Python SDK only. There is no create-webhook CLI command, the MCP webhook tools are hidden unless you start the server with --allow-webhooks, and the desktop app does not list your registered webhook subscribers, it offers only a webhooks on/off toggle and a local-target allowlist.
The AI Assistants (MCP) switch is not enforced by the gateway
The Integrations panel has an on/off switch for AI Assistants, but the gateway does not yet enforce it. An assistant that connected before you turn it off keeps working until you disconnect that client or its token is revoked.
On the roadmap
Planned, not yet shipped
- Opt-in expiry for the loopback and MCP tokens. The underlying optional-expiry plumbing already exists but is not yet exposed for these tokens.
Last updated on
Pairing and LAN access
Let another device on your network reach the gateway over HTTPS, with certificate pinning and in-app approval.
Manual Model Download
Stuck on Meetily's Step 1 or Step 2 download screen? Download the files yourself and slot them in. Works for non-technical users - no terminal required.