Beta

Known beta limits

These are the limits we know about today. We update this page as they are lifted.

Attachments

Attachments are not supported on the phone channel, the OpenAI-compatible endpoint (/chat/completions) or workflow chat. Files sent there are ignored without an error, so the agent answers without them.
Only TXT, MD, CSV, JSON and PDF documents (plus images) can be attached; Word and spreadsheet files cannot. Scanned PDFs without selectable text are refused.
Only the first 20,000 characters of a document, and 30,000 per message, reach the agent.

A tool that uses the end user's own token ("Forward the user's own token", FORWARD_TOKEN) or exchanges it (TOKEN_EXCHANGE) cannot run after an approval: the token is not kept while the call waits, so the approved call fails. Use "Forward who is chatting" (FORWARD_IDENTITY) for tools that need approval; it resumes as the same end user.
An approval nobody decides in time is rejected, never approved.

One-time deploy outputs (a key minted by an ApiKey resource) are held by the platform for 10 minutes, in memory only, for the key that deployed. If you miss them, or the platform restarts first, rotate the key.
DAK cannot set a knowledge base's indexing key yet: choose it once in the dashboard (or by API) after the first deploy, before loading documents.
The CLI runs your TypeScript with tsx, which does not check types: run tsc --noEmit before dak synth.

Knowledge bases are indexed with OpenAI embeddings on your own OpenAI key, even if your agents use another provider.
Documents uploaded to a knowledge base are limited to 10 MB each.

There are no ready-made agent templates in the agent builder yet; start from the builder or from a sample agent. (Multi-Agents has pipeline templates.)
Sign-in uses a 6-digit code sent by email for every password sign-in; authenticator apps are not supported. Google sign-in is available when it is set up for your organization during onboarding.
There is no self-serve sign-up: the Dezifi team creates your organization.