agent-control-center

Agent Control Center

Coordinate one task without confusing the controller, host, worker, model, or transport. Keep exactly one controller responsible for the plan, dispatch decisions, verification, and final acceptance.

Core invariants

• Treat the active application or CLI as the host. The host exposes tools and retains execution authority even when another provider is the controller.
• Treat a model as a capability behind a host, not as a controllable process.
• Keep the host parent as the user-facing relay and execution authority. An external controller owns orchestration decisions, but cannot widen host permissions or directly control native agents.
• Keep controller and worker provider, transport, model, and reasoning choices separate. Selecting a controller never assigns that provider as a worker.
• When an external controller is active, topology skills run in executor mode: the controller creates work orders and reviews receipts, while the host asks user questions, dispatches approved workers, and returns their receipts.
• Never claim that plain MCP lets a server click, control, or spawn agents in its client. Use host-mediated work orders and proof receipts.
• Give every worker a bounded scope, budget, expected artifact, validation, and stop condition. Do not permit recursive worker dispatch unless the work order explicitly allows one bounded child layer.
• Allow at most one controller transfer per task. Require user approval before a transfer changes provider, billing, permissions, or mutation authority.
• Preserve repository rules, protected paths, human gates, and user-owned changes across every provider boundary.

Inputs

Resolve these values before dispatch:

• objective: one observable outcome;
• controller: native, auto, or a registered provider identifier such as codex, claude, cursor, opencode, grok, or kimi; default to native unless the user requests cross-provider control or automatic selection;
• relay_mode: automatic-host-relay or sequential-host-relay for a non-manual controller transport; bind manual-handoff automatically when controller_route.transport=manual;
• controller_route: controller provider, transport, model, and supported reasoning effort;
• worker_routes: default or per-role worker provider, transport, model, and supported reasoning effort, selected independently from the controller;
• topology: plan-only, sequential, countercheck, parallel-analysis, verified-graph, or proofline;
• scope: repository root, allowed paths, protected paths, and external systems in scope;
• authorization: read-only or approved mutation boundaries;
• budget: lane count, time, retries, and any user-stated cost limit;
• acceptance: commands, artifacts, objective checks, and human gates.