Reference

Configuration reference

Every field of control-center.yaml, with its type, default and meaning. The Mac app generates this file for each project; you can also write it yourself.

The file#

Everything project-specific is configuration in one YAML file, control-center.yaml. The Mac app uses the file in your repository if one exists and points at it, or generates a private one in its own data. From source, acc looks for --config, then ACC_CONFIG, then control-center.yaml or control-center.yml in the current folder.

A minimal configuration:

project:
  name: example-app
  repo: ~/code/example-app
  checks: { test: "npm test" }
  check_runtime: { mode: docker, endpoint: unix:///var/run/docker.sock, image: example-app-checks:local }
tracker: { type: local }
agents:
  - { id: claude, name: "Claude Code", role: engineer, adapter: claude-headless }

The fully commented example is examples/control-center.yaml. Unknown or invalid values are reported with their path, for example agents.0.metered_opt_in: …, and the daemon does not start until they are fixed.

Top level#

project#

check_runtime#

mode: docker runs checks offline in a local container. See Project checks in Docker.

mode: host-fixture with an absolute fixture_repo exists only for the disposable demo and tests. It also requires an opt-in marker in that repository's Git folder. Never use it for a real project.

agents#

A list of agents. Each id must be unique.

Which harness runs which provider#

Models ending in -cloud or :cloud run on Ollama's servers and must use provider: ollama-cloud.

tracker#

Outbound trackers do nothing until live: true. See Trackers.

import_sources#

A list of read-only issue sources for Import issues. Each has id (lowercase, digits, dashes), name, type (github or linear), enabled (false), and repo for GitHub or team (and optional project) for Linear.

policies#

knowledge#

Optional. Connects an Obsidian vault or Markdown folder for shared notes and One Ask.

graphify#

Dictionary's own intake always uses AST extraction with LLM keys stripped, whatever semantic says.

code_host#

Optional, read-only. One of:

Both accept activated (false), host, scopes (an activated connection needs a host and at least one scope), poll_seconds (15 to 300), finding_issues (manual or rule), an optional webhook (secret_account: github-webhook or gitlab-webhook; max_skew_seconds; replay_window_seconds) and fixture_base (a loopback URL, for tests).

infra#

Optional, read-only hosting and database probes.

server#

Reserved sections#

routing (work type → agents in order of preference) and workflow (methodology kanban, scrum or waterfall, auto_start, wip_limit, review, auto_merge, sprint and phases) are parsed and validated, but the current engine does not act on them yet. Use the canvas to define how work flows.

Editing settings in the app#

Settings → Project and policies edits the selected project's configuration: branches, checks and their Docker runtime, model rules, stall thresholds, code-host and infrastructure drafts, Graphify, and redaction rules.

• Review settings changes creates an exact, expiring Decision. Confirm it to save. Settings, your answer and the audit events commit together and survive a restart.
• A stale or replaced draft cannot be applied, and settings cannot change while work is running or queued.
• Protected branches, required approvals, strict connector scope and the zero-extra-spend default cannot be removed through this editor.
• Saving runs no project code, contacts no provider, pulls no image and activates no remote integration. Code-host and infrastructure drafts are activated separately in Connectors.
• Repository identity and the Docker namespace stay bound to the project registered in the Mac app.