Harness Config
Canonical registry-driven harness configuration surfaces: sync manifest, MCP registry, and tooling policy.
3 registriesRegistry-driven configuration that projects repo sources into per-harness home and project surfaces. Edit canonical files under
config/, then sync withscripts/sync_agent_stack.py.
Registries
Section titled “Registries” sync-manifest Ownership ledger for canonical, generated, merged, symlink, and symlinked-entry surfaces.
mcp-registry MCP server definitions, MCPHub endpoints, and client projection rules.
tooling-policy Instruction sources, tool allow/deny policy, and harness-specific runtime defaults.
Workflow
Section titled “Workflow”- Edit the canonical registry under
config/. - Preview drift:
uv run python scripts/sync_agent_stack.py --targets repo,home --check - Apply projections:
uv run python scripts/sync_agent_stack.py --targets repo,home --apply
Related
Section titled “Related” Hooks Lifecycle hooks declared in config/hook-registry.json.
MCP servers First-party MCP packages and MCPHub control plane.
CLI wagents commands for validate, sync, and doctor workflows.