Skip to main content
Values come from the Bellows code. Where a value is set by whoever runs Bellows, the table says so. A request over a limit is refused with an error that names the field; it is not trimmed silently.

Tasks and prompts

See Writing good tasks and Task lifecycle.

Attachments

See Attachments.

.bellows.yaml

The schema is in .bellows.yaml reference.

Gates

A gate’s own timeout is also capped by the run time limit below. See Gates.

Services

See Services.

Policy and reviewers

See Policy and reviewers.

Executors and profiles

See Executors.

Skills

See Skills.

Environment variables and secrets

See Environment variables and secrets.

Tokens

See Install and sign in.

MCP

See MCP tools.

CLI

Exit codes: 0 ok, 1 refused, 2 usage, 3 wait ran out, 4 failed, 5 stopped, 6 waiting, 7 unreachable, 130 interrupted. See Command reference.

Run time and timeouts

Values marked “set by the operator” are the defaults. Whoever runs Bellows can change them.