Skip to main content

Limits

The fixed limits on agent calls, approval requests, input size and stored history, and the error each one returns.

The limits are on by default and fixed. They keep one connection from flooding the application and keep each call inside Convex's own limits. An agent that reaches one gets a code and a message that says what to do.

In-app agent runs are experimental in 0.1: their API may change in a minor release. The MCP door, tools and approvals are stable.
LimitValueWhen reached
Writes per agent connection60 a minuteRATE_LIMITED; the message says how many seconds to wait
Open approval requests per agent20RATE_LIMITED; the agent waits until people decide
IDs in the input of one call1,000TOO_LARGE, before the handler runs
Rows one approval request covers500TOO_LARGE; ask for fewer at once
Size of one approval request256 KiB, with its plan and inputTOO_LARGE; make the plan smaller, or split the work
Time to decide an approval request30 minutesAPPROVAL_EXPIRED; the agent asks again
Items per page of a tool1 to 100, 50 by defaultlarger values are cut to 100
Size of one MCP request64 KiBHTTP 413, before any tool runs
Rows in one activity list1 to 200, 50 by defaultlarger values are cut to 200
Stored result of a write, for replay64 KiBstored as { truncated: true, bytes }; the write itself is kept
Activity rowskept 1 yeardeleted by housekeeping
Decided approval requestskept 90 daysdeleted by housekeeping; the activity row records the decision
Finished in-app agent runskept 30 days, with their messagesdeleted by housekeeping
Length of a tool name1 to 64 letters, digits, _ or -error when the module loads
Text of an approval summaryone line, 300 characterslonger text is cut
Unclaimed upload links and files100 per agent connectionRATE_LIMITED; see Files from agents

Read tools have no rate limit. Convex's own limits apply to them, and a page reads at most 100 rows.

A refused call does not count against a limit: its transaction rolls back. Agents use the same limiter as the policy's limits: a bucket that refills continuously, not a fixed window.

Retries

A host may send a write twice, for example after a timeout. Give the call a request_id. The same request_id with the same input returns the first result; the write runs once. A request_id reused for a different call fails with REQUEST_ID_REUSED.

The same call while its approval request is open returns the same request. After the person declines, the same call gets APPROVAL_DECLINED, with or without its request_id, until the declined request would have expired (30 minutes after it was made).

Known gaps

  • A parent tenant does not see the open requests of the tenants below it. List them for each child tenant.