Harness Config

Registry-driven configuration that projects repo sources into per-harness home and project surfaces. Edit canonical files under config/, then sync with scripts/sync_agent_stack.py.

7 surfaces

Source of truth

These pages document the machine-first registries in config/. Generated client configs are derived at sync time — do not hand-edit live ~/.config mirrors unless you are debugging a one-off override.

Registries

token-efficacyLayer taxonomy, RTK/DCP/MCPHub posture, decision gates, one-tool-per-layer.

rtk-integrationRTK shell-layer policy, wagents rtk commands, stack sync --with-rtk, and usage-review lane.

sync-manifestOwnership ledger for canonical, generated, merged, symlink, and symlinked-entry surfaces.

mcp-registryMCP server definitions, MCPHub endpoints, and client projection rules.

plugin-skill-ownershipOne-owner rules for repo skills, native plugins, duplicate cleanup, and docs coverage.

starlight-plugin-stackAstro/Starlight plugin owners, compatibility ledger, enabled proof page, and defer rules.

tooling-policyInstruction sources, tool allow/deny policy, and harness-specific runtime defaults.

Workflow

1. Edit the canonical registry under config/.
2. Preview drift: uv run python scripts/sync_agent_stack.py --targets repo,home --check
3. Apply projections: uv run python scripts/sync_agent_stack.py --targets repo,home --apply

Related

HooksLifecycle hooks declared in config/hook-registry.json.

MCP serversFirst-party MCP packages and MCPHub control plane.

CLIwagents commands for validate, sync, and doctor workflows.