DOCS

Settings.

Project and global settings for Agent Manager: API keys, webhooks, default agents, integration credentials, and the toggles that shape how the board behaves.

Two scopes: global and project

Settings live in two places. Global settings apply to every project on this Agent Manager install — default models, fallback chains, the worker cap, login credentials. Project settings override or extend the globals for a single repo: which integrations that repo uses, which agents own which lanes, which webhooks fire, board behaviour that only makes sense for that codebase.

If you run a single project, the line is mostly cosmetic. If you run many — different clients, different stacks, different privacy postures — it matters: keep secrets scoped to the project that needs them.

Model provider keys

The crew needs API keys to call the models you pick. You bring your own keys; Agent Manager stores them locally and uses them only when calling the providers you configured. See Data & privacy for where they live on disk and how to back them up.

What you can set per provider

API key (stored encrypted at rest on your machine).
Optional base URL override — useful for self-hosted or proxied endpoints.
Default model for this provider — the first choice on the fallback chain.
Per-provider rate or spend cap (when the provider exposes the data).

Adding a key

Open Settings › Models.
Pick a provider from the list.
Paste the key. The crew tests the connection before saving.
Pick the default model that should lead the chain for that provider.

No key, no work for that provider. The crew quietly skips any provider whose key is missing and moves down the chain — so a half-configured setup still runs, it just runs narrower.

Default agents

Defaults are the agents a new project inherits when you spin it up. Tweak them in Settings › Agents and the next project you create starts from your preferred baseline instead of the factory one.

Default orchestrator — the boss that reads the inbox, splits work into tasks, and assigns owners.
Default specialists — the recurring roles you want on every crew (frontend, backend, docs, QA, and so on).
Default worker bot — the disposable bot specialists spin up for mechanical sub-tasks.

Projects can swap any of these locally without changing the global default.

Worker caps

Workers are the short-lived bots specialists spawn to grind through mechanical sub-tasks (running a test loop, mass-editing files, batch queries). They are powerful and they multiply quickly.

The global worker cap sets the hard ceiling on concurrent workers across the whole install. Lower it on a small machine; raise it on a box with cores to spare. Per-project caps let you protect the rest of the crew when one project goes busy.

Workers also stop automatically when the parent task ends — orphaned workers are reaped on the next heartbeat.

Integrations & webhooks

Anything outside Agent Manager that the crew talks to — Git hosts, messaging, databases, deploy targets — is configured here.

Credentials

Each integration has its own credential slot: API tokens, OAuth, webhook secrets. Scoped to the project that uses them, except for shared services (e.g. a single notification channel) which you can mark global.

Webhooks

Agent Manager exposes webhooks in both directions. Inbound webhooks let external systems push events onto the board (a CI failure, a new GitHub issue, a Twilio SMS). Outbound webhooks let the crew notify other systems when something happens on the board (a PR opened, a task escalated, a heartbeat missed).

Each webhook lists:

URL and method.
Trigger event(s).
Shared secret for signing payloads.
Per-webhook enable / disable toggle.

Board behaviour toggles

A handful of toggles shape how the board behaves day-to-day:

Heartbeat interval — how often the boss walks the floor. Default 30 minutes.
Escalation threshold — how many unanswered pings before the crew pages you on your phone instead of email.
Auto-merge on green CI — if your CI is the last gate, the crew can merge for you when it passes.
Branch protection — block agents from pushing to protected branches directly; require the PR route.
Default commit sign-off — append a trailer with the agent's name and the run id for auditability.
Quiet hours — suppress non-critical notifications between chosen hours. Escalations still break through.

Backup, restore, and exporting config

Everything in settings is plain files on disk. Backing up the config directory is the backup. See Data & privacy for the exact paths.

You can export a project's full settings (keys redacted) as JSON for sharing a non-secret baseline across installs. Useful for getting a second laptop to feel like the first.