Repo Settings
Repository settings live on each region’s Settings tab. Choose a repository with the repository control in the region’s header. With a repository in scope the tab shows that repository’s settings, and Show tenant settings switches to the tenant’s.
| Tab | Holds |
|---|---|
Standards → Settings (/standards/settings?repo=owner/name) | Workflow, standards set, analyzer, developer and reviewer models, review checks, timeout per check, required CI checks, CI check timeout, and the epic feature branches hint |
Autonomy → Settings (/autonomy/settings?repo=owner/name) | Intake mode, auto-merge, dependency updates, the autonomy grant and strategy settings |
Operations → Settings (/operations/settings?repo=owner/name) | Patience, agent authentication, Mayor routing, package feeds, budget ceiling, setup and prebuild commands, skip pre-push hook, setup, clone and dependency install timeouts, and base branch |
Config precedence
Section titled “Config precedence”A value set here overrides any value from a repository group, a group’s value overrides the tenant value, and the tenant value overrides Colony’s built-in default. When a repository is in several groups, the group ranked first wins. In short: repository, then groups by rank, then tenant, then built-in. A field you leave blank or on its inherited option falls through to the next level.
Edit the fields on a tab, then choose that tab’s Save settings. Nothing is stored until you save. Agent authentication and package feeds open in a drawer and save there.
Standards → Settings
Section titled “Standards → Settings”Workflow
Section titled “Workflow”Default, or one of the workflow definitions registered for your organization. The Default option runs the standard pipeline. Define workflows in Workflows settings, and see Workflow for the state machine this repository runs.
Model selection
Section titled “Model selection”Three selectors, Analyzer, Developer and Reviewer, override the tenant models for this repository. Each defaults to Tenant default, and each option lists the model’s name, whether it is the default, and its capability tier.
A model set on a workflow stage, or chosen by model routing, still takes precedence. See Model routing.
Review checks
Section titled “Review checks”The commands Colony runs during code review. Each check has a Name, a Command and a Blocking toggle.
- A non-blocking check is reported on the review but does not stop the change. Checks are blocking unless you turn the toggle off.
- Use the arrow buttons to reorder checks, + Add check to add one and Remove to delete one. Removing asks you to confirm.
- A check with an empty name or command shows an error, and Save settings stays disabled until you fix it.
Timeout per check and CI checks
Section titled “Timeout per check and CI checks”Timeout per check (on Standards → Settings) is how long a single review check command, such as test or lint, runs before it is killed, in seconds with a minimum of 1. A blank field uses the tenant default.
Required CI checks on Standards → Settings lists the CI check names that must pass before review; leave it unset to use the tenant value. CI check timeout sets how long review waits for them, from 60 to 86400 seconds.
Epic feature branches
Section titled “Epic feature branches”A hint, not a field. Epic feature branches are set for the whole tenant, in the Epic Execution section of Standards → Settings, where Colony groups subtasks under epic/N branches for coherent review. Open the tenant settings goes there. See Agent settings.
Autonomy → Settings
Section titled “Autonomy → Settings”Intake mode
Section titled “Intake mode”- All issues processes every new GitHub issue automatically.
- Tagged only processes only issues with the Colony label.
Tagged only is recommended when you share the repository with human contributors.
Auto-merge
Section titled “Auto-merge”When enabled, Colony merges the PR automatically after review passes. Disable it if you want a human to approve every PR before merge.
Dependency updates
Section titled “Dependency updates”Shown only when your tenant has dependency updates configured. It overrides the tenant’s dependency update settings for this repository only. A key you leave alone follows the tenant.
- Review dependency updates automatically
- Merge patch updates automatically
- Merge minor updates automatically (after Colony’s review)
- Auto-create migration issues for breaking changes
- Bot usernames — a comma-separated list of bot accounts whose changes Colony treats as dependency updates.
- Most dependency updates in progress at once — a whole number of 1 or more.
Each key carries a badge showing where its value comes from: Set on this repository, From the tenant or Built in. Use the tenant value removes the repository’s override. The three merge and migration options have no effect while automatic review is off, because Colony then ignores dependency updates.
Operations → Settings
Section titled “Operations → Settings”Agent authentication
Section titled “Agent authentication”A row on Operations → Settings shows how agents sign in for this repository, and Change opens a drawer (?setting=agent-auth).
Agents sign in with an API key, which is usage-based: Colony bills against your Anthropic account per token consumed, using your organization’s Anthropic key. Check and save checks that key with Anthropic first. If Anthropic rejects the key, or no key is stored, nothing is saved. If Colony can’t reach Anthropic, the setting is saved with a warning.
When the repository uses the API key but your organization has no key for the active Claude provider (Anthropic, Foundry or gateway), the row shows a no key yet chip and a link to model access, where you add one.
Mayor routing
Section titled “Mayor routing”Shown to people who can change the tenant’s pipeline configuration (org-pipeline-config-update). This row is read-only here. Change it in the tenant’s Operations → Settings (/operations/settings, or add view=tenant when a repository is selected), where Change opens a drawer (?setting=mayor-route) to route the Mayor through this tenant’s model access: its own Anthropic key, Foundry or gateway. Check and save tries the route first, and shows the provider’s error if it fails. Once it is on, a failed route is reported and never falls back to Colony’s key. The setting belongs to the organization, not to this repository.
The option is unavailable when the tenant uses workload identity federation, when no usable key or endpoint is set up, or when the organization has more than one connected tenant.
Package feeds
Section titled “Package feeds”Credentials for private package feeds, used during agent builds. Colony stores an Azure DevOps credential for the repository. It cannot validate the token without calling the provider, so an authentication failure shows up on the next worker run.
A row on Operations → Settings shows Not set, or the provider, organization and when the token was set. Owners and admins see Change, which opens a drawer (?setting=package-feeds) holding the fields below. Other roles see the row only.
| Field | Behavior |
|---|---|
| Personal Access Token | Required. A Show / Hide button reveals the value. |
| Organization | Required. Your Azure DevOps organization. |
| Package Feeds | At least one feed. Each has a URL (valid, required) and a kind, npm or nuget. An npm feed can also take an @scope. Use + Add feed and Remove. |
Choose Save to store them. Remove credential deletes them, after which Colony no longer authenticates with your private feeds.
Budget ceiling
Section titled “Budget ceiling”A read-only row showing the spend ceiling in force for this repository (“Effective ceiling: $N”), or No ceiling when none applies. When the tenant’s monthly ceiling is the binding one, the row adds “Set by your monthly ceiling”.
You do not edit budgets here. Budgets are authored on Operations → Settings (/operations/settings). See Cost and budget.
Setup command and prebuild command
Section titled “Setup command and prebuild command”Setup command runs in the cloned repository workspace before each agent task. Common uses are installing dependencies, building assets and setting up test databases. The placeholder is npm install.
Prebuild command runs after the setup command, to compile or build the repository before agent tasks. Use it for projects that need a build step before tests or type checks can run. Leave it blank if you have none.
Skip pre-push hook
Section titled “Skip pre-push hook”Bypasses git pre-push hooks when the agent pushes code. Enable it if your pre-push hooks need interactive input or credentials the agent does not have.
Timeouts
Section titled “Timeouts”All timeouts are in seconds, and the minimum is 1. A blank field falls back as shown:
| Field | Controls | Blank falls back to |
|---|---|---|
| Setup timeout (seconds) | How long the setup command runs before it is stopped. | The tenant default |
| Clone timeout (seconds) | How long cloning the repository runs before it is stopped. | Colony’s default, which applies no clone timeout |
| Dependency install timeout (seconds) | How long the toolchain dependency install (mise install) runs before it is stopped. | Colony’s default |
Base branch
Section titled “Base branch”The branch Colony’s work for this repository targets. It starts as the repository’s GitHub default branch, and the field shows that default beneath it (GitHub default: main). Type another branch name, such as dev, and save. Colony checks that the branch exists on GitHub before it saves, and shows an error on the field if it does not.
Once you set a branch, it stays set when you disable and re-enable the repository, and Colony no longer follows later changes to the GitHub default branch. Use GitHub default appears while a branch is set; it restores the GitHub default and lets Colony follow it again. Entering the GitHub default branch by hand does the same, so an override is recorded only for a different branch. Multi-repo workers pick up a change without a restart; a single-repo worker uses it after its next restart. Save it with Save settings.
Default stewards
Section titled “Default stewards”Default stewards are not on any Settings tab. The people Colony assigns to the items it creates when there are no parent assignees are set on Account → Tenants → your tenant → Repositories: each enabled repository’s row shows its default stewards, and tenant administrators choose Change. The person who enables a repository becomes its default steward when it has none.
Save settings
Section titled “Save settings”Save settings stays disabled until the tab has unsaved changes and every field on it is valid. On success a “Settings saved” message appears. If you leave the tab with unsaved changes, Colony asks you to confirm.