Skip to content

Limits ​

Every default limit, timeout, budget and cap in Casama, what happens when a run or call hits it, and whether you can change it. For what happens when a background or chat run ends at a limit, see When a run hits a limit; for live calls, see When a live call ends for a limit.

Runs, check-ins and budgets ​

LimitDefaultWhen hitCan you change it?Details
Steps per run40Run ends with max_steps_exceededNo (fixed)Usage
Steps per check-in (briefs and looks)8 (plus 8,000 chars per app read)Check-in ends with max_steps_exceeded; long app results are trimmedNo (fixed)Routines
Time per run30 minutesRun ends with wall_time_exceededNo (fixed)Usage
Bot per-run budget$1Run ends with budget_exceededYes (CLI, API, or a bot managing bots)Usage
Bot daily budget$10 (UTC day)Active runs stop and new runs are refused (daily_budget_exceeded) until midnight UTCYes (CLI, API, or a bot managing bots)Usage
Subagent budget and time20% of parent's remaining budget (min $0.01); 10 min default (up to 1 hr)Subagent stops and returns its status to the parentParent bot can ask for less budget or set time up to 1 hrBots together
Parallel subagentsUp to 5 at once (sharing 40% of remaining budget)Bot waits for the batch before starting moreNo (fixed)Bots together
Bot-to-bot delegation depth3 levels deepDeeper delegations or loops back to a bot already in the chain are refusedNo (fixed)Bots together
Loop guard3rd identical mutating step blocked; 5 failed steps in a row ends runRun stops with stuck_loopingNo (fixed)Autonomy
Waiting approval or screen takeover24 hoursRequest expires and counts as denied or dismissedNo (fixed)Autonomy
Connected AI app (ask_bot) and external A2A agent wait10 minutesCaller gets waiting_approval or a timeout statusNo (fixed)MCP, Bots together
Simultaneous runs per workspace5 active runs (20 per worker)Extra runs wait in queue until a slot freesSelf-hosted: RUN_WORKSPACE_CONCURRENCY, RUN_CONCURRENCYConfiguration

Tools, coding agents and computers ​

LimitDefaultWhen hitCan you change it?Details
Shell command timeout10 minutes (bot can request up to 1 hour)Command is stopped and returns a timeout error to the runBot can pass up to 3,600 s per commandComputers
Browser action timeout90 secondsStep fails with a browser errorNo (fixed)Computers
Browser lock wait across chats90 secondsSecond chat/bot goes on without the browser or tells you it's waitingNo (fixed)Computers
Desktop action timeout60 secondsStep fails with a desktop errorNo (fixed)Computers
Coding agent run30 min on a computer; 60 min in cloudAgent process or cloud task is stoppedBot or custom agent can set 1–120 minCoding agents
Coding-tool helper commands (install, git diff)2 minutesHelper step fails with a timeout errorNo (fixed)Coding agents
Computer idle sleep5 minutes without useHome folder is saved and computer stopsYes, per computer: 5, 15, 30 or 60 minComputers
Live view auto-pause5 minutes without input or bot workAsks Still watching?, then pauses stream so computer can sleepNo (fixed)Computers
Live view control handback15 minutes without inputControl returns to the bot automaticallyNo (fixed)Computers
Live view reconnect~45 secondsFalls back to screenshots with Try againNo (fixed)Computers
Restore pointsAutomatic ones 10 min apart; keeps last 20 or 7 daysRapid deletes skip extra auto points; oldest points are deletedBot or person can save a manual restore point anytimeComputers
Download all files zip1 GB (~/workspace)Larger folders can't be zipped in one downloadNo (fixed)Computers
Local companion command / question timeout10 minutes waiting for your answerQuestion expires and is treated as declinedNo (fixed)Your own computer

Voice, live calls and bot rings ​

Self-hosted server owners can change the call and ring limits in Admin console → Services → Call limits (or GET/PUT /v1/admin/call-limits).

LimitDefaultWhen hitCan you change it?Details
Quiet call hangup60 seconds with no speechApp hangs up (paused while a task runs or call is held)Admin console: silence_seconds (20–900 s)Voice
Longest live call60 minutesBot warns before end, says goodbye, and call closesAdmin console: max_call_minutes (5–240 min)Voice
Pre-limit warning~60 seconds before length or spend limitBot warns in one short sentence before wrapping upAdmin console: warning_seconds (15–300 s, max half call length)Voice
Abandoned call sweep60 seconds without an app heartbeatServer ends the call and settles billing (heartbeat_seconds 15 s, 5–60 s)Admin console: abandoned_seconds (60–900 s)Voice
Simultaneous billable live calls per workspace3 open callsNew call is refused with 429 too_many_callsNo (fixed)Voice
Live call start reserve (Casama Cloud)At least 2 minutes of creditsCall is refused (out_of_credits) before connectingAdd credits or upgrade planVoice
Bot ring timeout45 secondsStops ringing and sends a missed-call notificationNo (fixed)Voice
Bot daily ring cap3 rings a day across all botsStops ringing, sends a notification, and tells the bot whyAdmin console: ring_daily_cap (0–20; 0 disables rings)Voice
Per-bot ring cooldown30 minutes between ringsSame bot waits before ringing again; sends a notification insteadAdmin console: ring_cooldown_minutes (0–1440 min)Voice
Voice tool handoff~12 secondsLonger tools move to chat and the bot tells you when readyNo (fixed)Voice
Call context and personaFirst 1,500 chars of instructions; up to 20 prior turns (~600 tokens); ~5 min live rolling windowOldest live turns trim (8,000 → 3,000 tokens); everything stays saved in chatSelf-hosted: VOICE_CONTEXT_TRIGGER_TOKENS, VOICE_CONTEXT_TARGET_TOKENSVoice, Configuration
Read-aloud clip4,000 charactersLonger replies are read up to the capNo (fixed)Voice

When a live call ends for a limit ​

Unlike chat and routine runs (which end immediately with a failed-run code in When a run hits a limit), a live call tries to wrap up cleanly so you aren't cut off mid-sentence.

Before a call starts ​

On Casama Cloud (or any server enforcing billing/quotas), starting a call checks headroom before opening the session. If a limit is already hit, the call doesn't start:

  • Out of credits (out_of_credits): workspace has less than 2 minutes of call reserve left; the app opens the credits or paywall sheet.
  • Plan daily limit (cloud_daily_cap): Casama Cloud workspace reached its daily model/voice spend cap (resets at midnight UTC).
  • Workspace monthly quota (quota_exceeded): self-hosted workspace reached its monthly spend limit.
  • Bot daily budget (daily_budget_exceeded): the bot reached its daily budget for the UTC day.
  • Too many open calls (too_many_calls): 3 billable calls are already active in the workspace.

Mid-call ​

On relayed calls (Casama Cloud, or self-hosted with LIVE_CALL_RELAY=on), the server checks remaining time and headroom every 20 seconds:

  1. Warning (~60 seconds left): The bot gets a prompt to let you know in one short sentence that the call is about to hit its limit.
  2. Goodbye and clean close: When the limit is reached (or under 20 seconds of headroom remain), the bot says a short 1–2 sentence goodbye explaining why and noting that anything already started continues in the chat. Once playback finishes (at most 30 seconds), the server closes the call cleanly (the app does not auto-reconnect), settles usage, and posts the call recap card in the chat.
End reason (end_reason)Why the call ended
max_lengthReached the longest call limit (60 minutes by default)
creditsWorkspace ran out of credits
daily_capCasama Cloud plan hit its daily spending limit (resets midnight UTC)
quotaWorkspace hit its monthly spending quota
bot_budgetThe bot hit its daily budget (resets midnight UTC)
silentQuiet call idle hangup (60 s without speech or running tasks) or abandoned call sweep (60 s without app heartbeats)
hung_upYou (or another call replacing it) ended the call

On calls connected straight to Gemini with your own Google AI key (LIVE_CALL_RELAY=off), the server isn't in the audio path, so the app enforces the idle silence hangup and longest-call wrap-up itself, and the server's abandoned-call sweep handles dropped apps.

Notifications, workspaces and Casama Cloud plans ​

LimitDefaultWhen hitCan you change it?Details
Proactive non-urgent pushes5 per bot per day (user's timezone; brief excluded)Extra normal-urgency pushes wait in your inbox for the next morning briefNo (urgent pushes and replies don't count)Attention
Quiet hours22:00 to 07:00Non-urgent pushes and scheduled check-ins wait until quiet hours endYes, in Settings or per botAttention
Check-in share of daily limit (Casama Cloud)40% across all check-insCheck-ins stop for the day so your own chats keep headroomNo (fixed)Routines
Workspace invite codes and linksCode: 48 hours; email invite: 7 days; custom link: 1, 7, 30 days or never (1, 5, 25 or unlimited uses)Expired invites are rejected; wrong invite attempts lock for 10 tries in 10 minutesAdmins pick expiry/uses on custom linksWorkspaces
Casama Cloud workspaces per personUp to 5 owned workspacesCreating another workspace is blockedNo (fixed)Usage
Invite-a-friend rewardsUp to 20 rewarded friends ($2 credits each); code entry within 7 days of signupExtra invites don't pay credit rewardsNo (fixed)Usage
Self-hosted workspace quotasUnlimited unless setBlocks new bots or runs past monthly spend (quota_exceeded)Admin console → Workspaces → Edit quotasUsage

Casama Cloud plan caps ​

PlanBotsComputers (running at once)Computer hours / monthDaily model & voice limitPeopleLibrary storageCasama Link servers
Free31 (1)5$0.2511 GB1
Plus102 (1)30$5110 GB1
ProUnlimited5 (2)100$103 (+paid extras)50 GB3
MaxUnlimited10 (2)300$2510 (+paid extras)200 GB10

See Casama Cloud plans and credits for full plan rules, trial allowances and check-in frequency caps.