Crux Control discovers the agents already installed on your machines, governs their MCP tool calls, routes work across vendors, and gives operators one traceable command surface.
// Foundation scope - Plan 1
target baseline - 2026-05-12
// The questions vendor SDKs leave to operators
If agents are doing real work, they need a control plane before they become an unmanaged workforce.
// Control plane - core primitives
Crux is not another agent SDK. It is the operational layer that sits above every runtime: inventory, execution, policy, and trace.
Scan PATH and native MCP configs, register managed agents, then dispatch jobs with context packs through the `crux` CLI.
Capture subprocess output, execution status, trace events, cost estimates, and handoff records in one local control plane.
Inject the Crux MCP gateway so managed agents route tool calls through allow, deny, approval, and audit policy.
Bring SDK-built agents through Crux-owned adapters and model gateways for deeper model-call observability and routing.
// Five pillars
Crux organizes the operational layer: inventory, governance, portability, observability, and release discipline across vendors and frameworks.
// Crux console - operator surface
Inspect a run, see the agent that handled it, review MCP tool calls, approve risky actions, and hand work to a fallback agent with the full context pack intact.
$ go install github.com/agenticfleet/cruxcontrol/cmd/crux@latest==> Building crux from source==> Installed -> ~/go/bin/crux$ crux up✓ crux server running on http://localhost:7700
apiVersion: crux.io/v1alpha1kind: Fleetmetadata:name: support-triagespec:agents: { min: 4, max: 64 }gateway: { policy: prod-guardrails }observability: { otel: true }
// Platform surfaces
Start with the local `crux` CLI and grow into gateways, fleet dashboards, Kubernetes, and cloud synchronization without changing the operating model.
// Bring any agent. Keep its native auth.
Crux sits above your installed CLIs, SDK-built agents, providers, and MCP servers. It governs the operational boundary without replacing the framework.
Agents and frameworks
Model providers
Runtimes
// Use cases
Find installed CLI agents and custom agents, import their metadata, and track owners in one fleet.
Proxy MCP tool calls through allowlists, blocks, approvals, audit trails, and prompt-injection scans.
Hand a job and its packed context from one agent to the next when a run fails, stalls, or reaches limits.
Estimate and attribute execution cost from captured traces without taking over provider authentication.
Export, import, and promote known-good agent, policy, MCP, and model-route profiles across machines.
Queue risky tool calls for review and preserve the decision in the execution trace.
// Pricing
The Apache-2.0 core is complete enough to self-host. Commercial tiers add hosted operations, retention, org controls, support, and fleet-scale compliance.
Local Crux CLI, server, worker, gateway, MCP governance, console, adapters, and exports.
Hosted control plane for small fleets that need sync and short retention without running infrastructure.
The organization tier for shared fleets, policy rollout, approvals, SSO, and audit export.
Dedicated hosting, regulated retention, support, and hardened delivery for large or sensitive fleets.
Crux Enterprise packages the cloud operations layer for air-gapped and dedicated environments with hardened images, policy packs, and compliance evidence.
Start with local discovery and execution. Add MCP governance, traces, approvals, and cloud sync when the fleet grows.