Skip to main content

Limits

The numeric bounds on task execution, governance and the authorization graph. Every value below is the value in source; overrides are listed per limit.

Synopsis

A limit comes from one of three places, and that decides how you change it.

Fields

Values

Policy ceilings

Execution limits

The effective policy must contain run budget, total and per-call token ceilings, model turns, per-turn tool calls, and total tool calls. Missing dimensions reject task execution rather than selecting a code default. The values above are seed data for a new workspace and become rows in the policy database; operators may replace the seed file and existing workspace rules are not silently overwritten.

Guard thresholds

Warning fires at the ratio; denial fires at full consumption.

Timeouts

There is no timeout on a pending human approval.

Retries

LLM calls retry transient failures with backoff. Permanent failures — auth, quota, billing, an unknown model — fail fast via a non-retryable flag.

Concurrency

There is no per-workspace request rate limit, task concurrency quota, or tool call rate limit.

Context window management

Output offloading

Event-log bounds

Applied to Redis and database event projections. Activities and the model still receive the original values. Field names matching a secret pattern are replaced with [redacted]. Fields carrying content, command text, stdout or stderr are replaced with a size marker.

Pagination

Enforcement

The max_depth parameter on the graph client’s check accepts a value and defaults to 10, but it is not sent in the request. Setting it has no effect.

Defaults and overrides

Where a default exists in more than one place, the code default is authoritative for a process started without the corresponding environment variable. make up runs docker-compose.yaml and make up-dev runs docker-compose.dev.yaml. On the make up path the graph backend is disabled, in which case every permission check returns allow. Every constant listed under Values that is not shown with an environment prefix is a code constant with no override.

Example

Tighten one task below the workspace ceiling. The effective run budget becomes the minimum of the request value and every layer above it:

See also