Configuration reference

Environment variables

These are read at startup and override defaults without requiring a code change.

CAPS

The CAPS object in lib/config.mjs controls all cycle timing and per-cycle dispatch limits. Every cap is a hard bound — once hit, no further mutations of that type happen in that cycle. Can be overridden entirely via the AURIGA_CONFIG external file.

// Example: external override file to slow the cycle
{
  "CAPS": {
    "perCycleTotal": 3,
    "cycleMs": 120000,
    "zombieMaxAttempts": 2
  }
}

HUMAN_NAMES

The list of human names that trigger the human-todo filter. An issue with waiting_on: <value> in its metadata is excluded from agent dispatch if value case-insensitively contains any name in this list.

// Default in lib/config.mjs
export const HUMAN_NAMES = _ext.HUMAN_NAMES ?? ['mathew', 'dostal'];

// Override via AURIGA_CONFIG:
{ "HUMAN_NAMES": ["mathew", "dostal", "alice"] }

Add a name here when a new human joins the team and needs issues flagged for their attention routed to the human queue instead of an agent lane. See Human-todo filter for full semantics.

REVIEW_SQUAD_RULES

The explicit, inspectable rule table that reviewSquadPlan(issue, cfg) uses to size the review squad for each ticket. Keyword lists classify issues into tiers; the tier determines which perspectives run and whether Playwright is required.

// lib/config.mjs — edit keyword lists to change how tickets are sized
export const REVIEW_SQUAD_RULES = _ext.REVIEW_SQUAD_RULES ?? {
  ui: ['ui', 'ux', 'page', 'react', 'dashboard', 'css', ...],
  backend: ['api', 'endpoint', 'router', 'service', 'schema', ...],
  light: ['docs', 'readme', 'chore', 'config', 'typo', ...],
  tiers: {
    full:     { product: true,  technical: true, qa: true, ux: true,  playwright: true  },
    backend:  { product: true,  technical: true, qa: true, ux: false, playwright: false },
    light:    { product: false, technical: true, qa: true, ux: false, playwright: false },
    standard: { product: true,  technical: true, qa: true, ux: true,  playwright: true  },
  },
};

Classification scans the issue title and description for keywords. The first matching tier wins. If no keyword matches, the issue gets the standard tier (full four perspectives). No code change is needed to tune the keyword lists — update them in the override file via AURIGA_CONFIG.

AGENTS

The agent registry in lib/config-substrate.mjs. Maps agent IDs (Multica UUIDs) to agent metadata used during dispatch.

// Each entry in AGENTS:
{
  "<uuid>": {
    name:       "auriga-build",    // display name
    runtime:    "claude",          // runtime bucket for RUNTIME_CAP
    maxInflight: 3,                   // max concurrent in_progress issues
    lane:       "hive",            // routing lane (optional — overrides PROJECT_LANE)
  }
}

Add an entry here when a new agent joins the swarm. The runtime field must match a key in RUNTIME_CAP. The maxInflight per-agent cap is checked independently of the per-runtime cap — both must have room for an issue to be dispatched to that agent.

RUNTIME_CAP

A map from runtime bucket name to the maximum number of concurrently in_progress issues that bucket can hold. Defined in config-substrate.mjs and mutated in config.mjs to add the review bucket.

// config-substrate.mjs — base runtime caps
export let RUNTIME_CAP = {
  claude:          4,
  codex:           6,
  opencode:        4,
  'claude-planning': 1,
};

// config.mjs — review gets its own bucket
RUNTIME_CAP['claude-review'] = 1;

The runtime cap check is: count the in_progress issues assigned to all agents in the same runtime bucket, then compare against the cap. If the bucket is full, no further dispatches happen to any agent in that bucket this cycle.

Lane configuration

Lane maps are in config-substrate.mjs. They determine which Multica agent lane receives each dispatched story.

External JSON override

Set AURIGA_CONFIG=/path/to/override.json to a JSON file with partial overrides. Only keys present in the file replace the in-source defaults — absent keys keep their values from the source files.

# Start with a custom config file
AURIGA_CONFIG=/etc/auriga/prod.json node src/router/auriga-router.mjs

// /etc/auriga/prod.json — only override what differs from defaults
{
  "CAPS": {
    "perCycleTotal": 8,
    "cycleMs": 60000
  },
  "HUMAN_NAMES": ["mathew", "dostal", "alice"],
  "RUNTIME_CAP": {
    "claude": 6,
    "claude-review": 2
  }
}

The override is processed at startup by lib/config-loader.mjs via loadExternalConfig(). If the file path is invalid or the file is malformed JSON, the router logs a warning and uses the built-in defaults.