Account settings

Account settings apply across sessions and automations. Owners and organization administrators manage financial settings with their user credentials. API keys and sandbox credentials cannot change those settings.

Model and session defaults

Setting	Effect
Default model	Used when a Claude Code session omits `claude_code.model`
Session budget ceiling	Rejects requests that ask for a larger session budget

Changing the default model affects new sessions. Codex uses its own default model. There is no default environment.

Spend limits

Open Billing > Limits to set account limits and optional developer limits.

Limits track actual Ellipsis credit usage over trailing 1-, 7-, and 28-day windows. Developer attribution includes user activity and API keys.

An automation or handler can set additional limits in session.budget. All applicable limits must have room before another paid request starts.

A limit is a threshold for new paid requests. Outstanding requests and sandbox teardown can add usage after it is reached. Lowering a limit can stop paid requests in sessions already running.

Platform allowances

Open API > Limits to see your account's API request limits, storage quotas, concurrency limits, and spending ceilings. Each row shows its scope and current allowance. Custom allowances are marked Custom.

Every API request counts toward the account total. An endpoint limit adds a cap for that endpoint; endpoints without a separate cap share the account total. Your own budgets can impose lower spending limits than the platform allowances.

To request an increase, open Help, create a shared Slack channel with the Ellipsis team, and ask there. If you already have a shared channel, use it. These allowances are assigned by Ellipsis; customer credentials cannot raise them through the settings API.

Budget alerts

Configure thresholds under Billing > Limits. Alerts appear under Settings > Alerts, with notification delivery controlled by the account's settings.

Use GET /v1/account/budget to inspect current limits and remaining spend.

Retention

See Security for session retention limits and the data deletion SLA. Export records you need before their TTL expires.

Shared configuration

A GitHub repository named .ellipsis holds organization-wide configuration. Its root is the configuration directory:

.ellipsis/
  automations/nightly-tests.yaml
  environments/api-environment.yaml
  github.yaml
  slack.yaml
  linear.yaml
  sentry.yaml
  code_review.yaml

Here .ellipsis is the repository name. Ordinary repositories store configuration inside a directory named .ellipsis/.

Each integration file defines exactly one responder: its name and identity under ellipsis, its filters under github, slack, linear, or sentry, and its execution settings under session. Multiple integration files for the same platform are not supported. Handlers support the same per-session and trailing budgets as automations; automation output schemas are not supported. Automations and environments keep their own document formats.

Credits and billing

See Pricing for credits, compute charges, and automatic recharge.