Agent Orchestration Platform
Start here when you want the hosted NFLTR overview. This page explains how planners, remote workers, dashboard operators, timeline reads, managed capabilities, and secure routing fit together on nfltr.xyz.
Sign up on nfltr.xyz, create an API key, and install the nfltr CLI before you follow the workflow below.
What changes when NFLTR is the platform layer?
Planner Registration
Register one hosted MCP entry in the workspace so the local planner can orchestrate remote workers through nfltr.xyz.
Worker Execution
Start workers with explicit role labels and local MCP commands such as nfltr copilot-mcp or other compatible tools.
Operator Visibility
The dashboard exposes a control tower summary, run explorer panels, role coverage, terminals, managed capabilities, and route inventory in one operator console.
Timeline Reads
Use get_orchestration_timeline or nfltr orch status --task ... --events 20 --watch to inspect one compact task view instead of stitching separate APIs manually.
Recovery
Resume or re-dispatch nonterminal work with planner-local state and coordination bundles instead of minting duplicate tasks blindly.
Secure Transport
Verified routing, private shares, direct hostnames, browser terminals, and traffic capture still exist underneath the orchestration layer.
Core workflow
- Register the planner:
nfltr mcp --proxy-url https://nfltr.xyz --write-mcp-json .vscode/mcp.json - Start workers with explicit labels and task slots:
nfltr worker --labels role=implementer --mcp-command "nfltr copilot-mcp" --max-tasks 2 - Dispatch work with orchestration tools such as
orchestrate_task - Inspect one compact task view with
get_orchestration_timelineornfltr orch status --task ... --events 20 --watch - Use the dashboard for operator readiness, managed surfaces, route inventory, and terminals
Where this is better than one local agent loop
| Need | Why NFLTR helps |
|---|---|
| Cross-machine execution | Workers can run on other machines and networks while the planner keeps one hosted control-plane entrypoint. |
| Role-aware dispatch | Workers advertise labels such as role=implementer or role=verifier so dispatch intent is explicit. |
| Operator inspection | The dashboard and timeline helpers give operators a concrete surface for readiness, history, and route state. |
| Recovery and handoff | Planner-local recovery and coordination bundles make resume or redispatch possible without ad hoc glue. |
Next reads
- Getting Started — sign up, install the CLI, and dispatch your first hosted task.
- AI Agent Orchestration — end-to-end planner-worker tool surface.
- Local Agent Orchestration — local-first operator walkthrough.
- Local Repo Improvement — isolated worker clones and git-backed patch return.
- Dashboard — operator console for readiness, terminals, traffic, and managed surfaces.
- Managed Capabilities — dashboard-driven desired state for long-lived surfaces.
Use NFLTR as the orchestration layer
Start with the hosted planner entrypoint on nfltr.xyz, bring workers online, then let the dashboard and timeline tools handle the operator view.
Read Orchestration Guide Getting Started Open Dashboard Homepage →