MASAKA / Operations / Limits
Boundaries you can
design around.
Limits protect task isolation, spending, storage, and shared capacity. Deployment configuration may lower a maximum.
Current limits
| Area | Contract |
|---|---|
| Session duration | 30–900 seconds, deployment-capped |
| Concurrent sessions | Account limit, separate from elastic fleet capacity |
| New-user trial | Three full agent/browser experiences; one account per network/IP policy |
| Browser downloads | 100 per session |
| Pending task attachments | Five supported text files, 200 KB aggregate UTF-8 |
| Generated text artifact | Markdown/TXT/CSV/JSON, 200,000 UTF-8 bytes each |
| Self-service booster | $10 minimum, $100 maximum, $19 default |
| Tab handle | 1–256 safe opaque characters returned by MASAKA |
Rate limits
Reads, writes, browser input, and command polling have separate buckets. A 429 response is safe to retry only when the original operation is a read or otherwise known not to have mutated state.