Use nfltr.xyz as the hosted control plane: register planners, run workers with MCP tools, watch timelines, and approve or reject inline. Tunnels stay available when a client needs HTTP, TCP, or SSH reach—but orchestration is the product.
Quickstart — start explicit task contracts and watch progress:
nfltr orch start task --task-mode generate-artifact --objective "Ship docs that lead with orchestration" --watch
nfltr orch start task --task-mode implement --objective "Implement the selected slice" --watchStart with Agent Orchestration. Also supports HTTP, TCP, and SSH tunnels for client connectivity when orchestration workflows need operator reach.
Follow these guides in order to go from first dispatch to multi-agent orchestration and team operations.
Sign up on nfltr.xyz, install the CLI, start a worker, and dispatch your first orchestrated task.
Guide 00Single-task workflow: objectives, execution roles, progress, and terminal results.
Guide 01Parallel slices, phased handoffs, decompose, verify, and loop decisions.
Guide 02Observe fleet readiness, run timelines, and operator approvals on the hosted dashboard.
Guide 03Shared labels, pools, dashboard visibility, and approval gates for squad workflows.
Guide 04Fix offline workers, queued tasks, rate limits, and transport drops from user-visible signals.
Guide 05Screenshot walkthrough of the Causal Operations Atlas: causal canvas DAG, task drawer, attention rail, and live fleet readiness.
Guide 06Operator console and slash-command tutorial for the interactive nfltr orch TUI.
Read Intent, Path, and Outcome for an ImprovementCampaign with nfltr orch campaign story.
Checkpoint readiness, failure signals, and contract/policy dry-runs before starting autonomous improvement.
GuideConnect workers across machines, advertise labels, and fan out work with capacity-aware dispatch.
Guide 08Hosted overview for task contracts, timelines, dashboard operators, and the recommended evaluator path.
CoreOperator console for orchestration readiness, managed routes, browser terminals, traffic inspection, and fleet controls.
CoreCommands for nfltr orch, planners, workers, secure transport, and dashboard-managed flows.
Coordination contracts between workers when tasks need artifact exchange, handoffs, or verification loops.
CoreHonest decision guide: when orchestration fits, and hosted nfltr.xyz versus a production standalone GCE VM with embedded web/; Kubernetes/Helm/make deploy-ui are legacy/non-production.
Watch the Causal Operations Atlas (attention rail, causal canvas, task drawer, Trace Lab) and metrics on nfltr.xyz—kick off from a laptop, follow from your phone.
GuideLocal Rust/Wasm analysis of wall time, critical path, quiet intervals, and earliest failure evidence—traces stay in the browser.
GuideIntegrate from CI or portals with curl: dispatch, status, Server-Sent Events, and results over the hosted REST API.
GuideRun the dashboard with mock OAuth, disposable state, protected API curls, and a filesystem-served UI edit loop.
GuideConfigure wildcard DNS records for direct hostnames and verified E2EE hostnames shown in the dashboard catalog.
GuideUse label selectors, fleet tokens, and capability-aware rollout patterns for larger worker populations.
CoreExpose local or managed HTTP services when orchestration workflows need a reachable endpoint.
AlsoReach SSH, databases, and private ports behind NAT or firewalls alongside orchestration.
AlsoSecure transport and verified routing under the orchestration and dashboard layers.
AlsoUse label selectors, fleet tokens, and capability-aware rollout patterns for larger worker populations.
CoreEmbed agents in Go applications and manage runtime behavior programmatically.
Reference