Documentation
Limits
These are the limits in this release, read from the service's own configuration. Daily limits reset at 00:00 UTC. An administrator can raise an account's limits.
Per account
| Storage connections | 25 |
| Drives | 50 |
| Mounts per drive | 16 |
| Active connections per drive | 100 |
| Share links per drive | 50 |
| Background jobs running at once | 3 |
Per day
| MCP requests | 50,000 |
| Shell runs | 5,000 |
| Code Mode runs | 1,000 |
| Bytes streamed between providers | 200 GiB |
| Background jobs started | 200 |
Per call
| Whole-file read | 4 MiB; larger files need a byte range or a download link |
| Write | 32 MiB; larger files need an upload link |
| Edit | 4 MiB file size |
| Folder listing page | 1,000 entries |
| Search and find | 50,000 objects scanned; 2,000 files and 64 MiB read for content search; 500 matches |
| Copy, move or delete per step | 1,000 objects or 2 GiB |
| Inline copy time | 20 seconds, then a background job |
| MCP request body | 4 MiB |
Shell and Code Mode
| Shell command line | 30 seconds; 60,000 characters of output |
| Code Mode run | 45 seconds; 1,000 drive calls; 64,000 characters of result |
Links, tokens and sessions
| Signed link lifetime | 15 minutes by default; the drive's cap is 24 hours unless changed, at most 7 days |
| Dashboard upload | 100 MiB |
| Agent access token | 60 minutes by default, 5 minutes to 24 hours per drive |
| Sign-in code | 6 digits, 10 minutes, 6 attempts |
| Browser session | 30 days |
| Waitlist entry | 180 days |
When a daily limit is reached, calls that need it fail with a LIMIT_EXCEEDED error that says when the limit resets, and other tools keep working. When the account runs out of MCP requests, the drive answers with HTTP 429 until 00:00 UTC. The dashboard's Home page shows today's usage.