Team Collaboration

Teams share the hosted control plane at nfltr.xyz: API keys, worker labels, and dashboard visibility for planners, workers, and reviewers.

Shared API keys

$ nfltr config add-api-key rpc_your_personal_key

$ nfltr config add-api-key rpc_shared_demo_key --name team-demo

$ nfltr config use-api-key team-demo

Who can see what

Same-tenant users typically see all fleet workers, orchestration DAGs, and task drawers—including objectives and results. Treat objectives as team-visible; use artifacts for secrets.

$ nfltr orch task status --task task-shared-abc --events 3

Label conventions

Use capability labels such as nfltr.supports_task_mode.implement=true, nfltr.worker.tool=run_task, pool=, and env=staging consistently so explicit task contracts land on the right worker.

Control tower

Link task_id and #task= URLs in chat. Use artifact_request / artifact_offer for handoffs. Production gates pause until a human approves in the drawer.

Related: Dashboard walkthrough.

Practical tips

NFLTR persists task history on the hosted control plane at nfltr.xyz, so reconnecting planners and dashboard viewers see the same timeline. Share runs with teammates using task ids and dashboard deep links instead of pasting full JSON envelopes. For production-impacting objectives, configure approval gates so a human confirms in the Atlas attention rail / task drawer before work continues. Combine the CLI examples above with the Causal Operations Atlas (causal canvas, Trace Lab) when you need mobile monitoring or inner-LLM turn detail documented in the observe orchestration guide.

Bookmark the docs index and feature pages when onboarding new teammates to the same hosted tenant.