Skip to content

Organization Pipeline Defaults (Agents)

The Agents settings page (/settings/agents) is the org-level editor for Colony pipeline and agent configuration. Changes here write to tenants.config.* in the Colony Cloud database and become the default for every repository in your organization. Repo-level settings can override any field; see Merge precedence below.

For the complete field catalogue (all ~100 fields, types, and defaults) see the Configuration schema reference. For cost tuning and model routing guidance see the Tune Model Routing and Cost Caps guide.

The page is divided into the following sections, accessible via the in-page section navigator:

SectionDescription
Claude ProviderAPI provider (Anthropic direct or Azure Foundry) and endpoint settings
ClaudeCLI timeout, inactivity timeout, and API retry count
ModelsPer-role model overrides (Developer, Reviewer, Analyzer, Planner, Merger)
ScalingPer-complexity-tier model, effort level, and developer turn limits (small / medium / large)
Agent Turn LimitsDeprecated per-role max-turn overrides (use Scaling tiers instead)
Model RoutingTask-type × complexity-tier model routing matrix and global override
EnginePer-agent execution engine selection (Claude Code or OpenAI Codex) and Codex CLI settings
ReviewAuto-merge, CI requirements, review checks, diff limits, and external PR review
AgentsMayor poll interval, heartbeat timeout, and issue intake mode
CostsPer-issue and daily USD cost caps
WorkspaceWorktree cleanup, stale-worktree pruning, and setup timeout
LabelsColony-managed label prefix
White-LabelSlash-command root prefix
WorkersWorker heartbeat interval, task retry limit, and task duration deadline
Epic ExecutionFeature-branch strategy, subtask rebase, and final-PR review policy
DependabotAutomatic review and merge policy for Dependabot PRs
Self-ImprovementAutonomous self-improvement issue generation
Pattern MemoryFew-shot pattern retrieval from past issue resolutions
Code BoundariesForbidden and read-only path globs for the developer agent
SLA ThresholdsPer-state warn-after-minutes thresholds (surfaced on Inbox)
Conflict ResolutionLLM-assisted merge conflict resolution via the merger agent
Advanced: ExecutionRepo context bundle, plan-file gate, overlap threshold, and per-executor effort overrides
Advanced: ReliabilityMayor auto-unblock, sync intervals, and starvation thresholds
AttributionEU AI Act Article 50(1) disclosure footer
IntelligenceRepo intelligence auto-promotion thresholds and embedding settings
RetrievalVector-search retrieval: enable, injection, per-role enablement, token budget, and snippet limits (intelligence.retrieval.*)
Code MapAnalyzer code-map snapshot: enable, injection into prompts, token budget, and minimum confidence (code_map.*)

The tables below cover the highest-impact fields. All other fields are documented in the Configuration schema reference.

Controls how much Colony may spend on Claude API calls before halting work.

FieldConfig keyUnitDefaultDescription
Max cost per issueclaude.max_cost_per_issueUSDnoneColony halts the task when this per-issue ceiling is reached. Set to 0 or leave blank for no limit.
Max daily spendmax_daily_usdUSDnoneGlobal daily ceiling. All pipeline work halts when exceeded and automatically resumes at the next UTC midnight.

Colony classifies each issue as small, medium, or large based on the analyzer’s complexity estimate. Each tier has independent model, effort, and turn-limit settings.

TierFieldConfig keyDescription
small / medium / largeModelclaude.scaling.<tier>.modelOverride the Claude model for this tier. Leave blank to use the global model setting.
small / medium / largeEffortclaude.scaling.<tier>.effortReasoning effort level: low, medium, high, or max. Higher effort uses more tokens but produces better results on complex tasks.
small / medium / largeDeveloper max turnsclaude.scaling.<tier>.developer_max_turnsMaximum conversation turns the developer agent may take for issues at this tier. Each turn is one Claude Code CLI invocation. (turns)

Additional per-tier fields (backstop_max_turns, no_progress_window, planning_max_turns) are documented in the Configuration schema reference.

Controls which issues Colony picks up for processing.

FieldConfig keyValuesDefaultDescription
Intake modeagents.sprint_master.intake_modeall | taggedallall processes every new issue automatically; tagged only processes only issues that carry the Colony intake label.

Controls how managed Colony Workers communicate with the Cloud API and how long a task may run.

FieldConfig keyUnitDefaultDescription
Heartbeat intervalworkers.heartbeat_intervalsecondsSeconds between Worker heartbeat pings to the Colony Cloud API.
Max task retriesworkers.max_task_retriescountMaximum consecutive failures for a repo + issue + task-type combination within 60 minutes before the task is permanently dropped.
Max task durationworkers.max_task_durationminutes45Wall-clock deadline per task. Workers abort and fail the task if it exceeds this limit.
Stale task thresholdworkers.stale_task_thresholdminutes3Minutes a claimed task may go without a heartbeat before a Worker’s sweep reclaims it and requeues it for another Worker. Distinct from the Mayor’s Heartbeat timeout, which applies the same reclaim check on the Mayor’s sweep — raise both together to reliably delay reclaim.

The Engine section lets operators switch any agent role to the OpenAI Codex CLI on a per-role basis. By default, all roles use claude-code (the Claude Code CLI). Setting agents.<role>.engine: codex routes that role’s tasks to the Codex CLI instead.

Codex is opt-in — switching a role requires:

  1. The OPENAI_API_KEY secret to be configured in Settings → Secrets.
  2. Codex model IDs (e.g. codex-1, o4-mini) to be set in the Codex model fields if you want to override the CLI default.
  3. A Worker redeploy after saving — engine selection is read on startup and is not hot-reloadable.

claude.models.* and claude.scaling apply only to Claude Code-engine roles. When a role runs on Codex, configure its model via codex.models.<role> instead.

For the complete field reference see ## codex and Engine selection in the Configuration schema reference.

This page edits the org-level (tenants.config) layer. The effective value for any field follows:

repo_configs.field ?? tenants.config.field ?? hardcoded default

Repository-level overrides take precedence over org-level defaults, which take precedence over Colony’s built-in defaults. Repo-level settings are configured per-repository under each repository’s Settings tab. Omitting a field at the repo level inherits the org default set here.

ActionRequired role
View org pipeline configurationOwner or Admin
Save org pipeline configurationOwner or Admin

Both GET and PUT /api/orgs/:orgId/pipeline/config require the owner or admin role (requireOrgMembership('owner', 'admin'), packages/api/src/org-routes.ts:1664,2053). The Agents settings page is only reachable from the admin-only scope in the settings navigation.

MethodPathAccessDescription
GET/api/orgs/:orgId/pipeline/configOwner or AdminFetch the current org-level pipeline configuration.
PUT/api/orgs/:orgId/pipeline/configOwner or AdminSave the org-level pipeline configuration.