Dashboard Admin

Use this page when you already know your path. On nfltr.xyz, the dashboard is the hosted console for orchestration readiness, managed capabilities, browser terminals, and fleet controls. It has four views: Agents (your hubs as the relay sees them: online or offline, last seen, the reattach command), Machines (joined machines, free slots, what each can run, and the agent catalog), Runs (a pointer to where your runs are: on your hub's machine, end to end encrypted), and Account (API keys and settings). Platform admins also get Admin. See the Dashboard walkthrough.

Sign in with Google, then open the hosted operator console at nfltr.xyz/dashboard. The dashboard reads no hub content: steer or stop a hub agent by asking its hub, and see its runs on the hub's machine with nfltr orch hub runs and nfltr orch hub show (see Agent Orchestration).

Access

The hosted dashboard is available at /dashboard after you sign in:

Surface	URL
Hosted operator console	nfltr.xyz/dashboard

Features

🧭 Orchestration runs

The Agents view lists your hubs by presence only. Runs stay with the hub, end to end encrypted: Runs lists the commands that show them (nfltr orch hub runs, nfltr orch hub show, nfltr orch --hub-id). See Observe orchestration.

📡 Agent Management

The agent catalog under Machines: connected agents with live badges (Browse, TCP, SSH, Term), routes, labels, uptime, and share URLs. Disconnect agents with one click.

🧠 Managed Surfaces

Stage AI, terminal, command, and HTTP capabilities as desired state and keep the operator-facing route catalog visible next to them.

💻 Browser Terminal

Open an xterm.js SSH terminal to any connected agent directly from the dashboard. 256-color support, resize tracking, 10K-line scrollback.

🔑 API Key Management

Generate, list, and revoke API keys under Account. No CLI access needed.

🏷️ Fleet Tokens

Platform admins create fleet tokens with label selectors, list active tokens, and delete expired ones under Admin.

📊 Server Stats

For platform admins, under Admin: connected agents, uptime, and health status at a glance.

Agent Badges

Each agent card shows capability badges based on its tunnel type:

Badge	Meaning	Action
Browse	HTTP endpoint available	Click to open in browser
TCP	TCP tunnel active	Shows `tcp-connect` command
SSH	SSH access available	Shows SSH/SCP/SFTP commands
Term	Browser terminal available	Click to open xterm.js terminal

Browser Terminal

Click the Term badge on any agent running nfltr shell to open an interactive SSH session in your browser:

Full xterm.js terminal emulation over WebSocket
256-color support and Unicode rendering
Automatic terminal resize tracking
10,000-line scrollback buffer
Copy/paste support

The terminal connection is routed over the TCP tunnel to the agent's embedded SSH server — no additional port forwarding or SSH client needed.

Managed Capabilities

For dashboard-owned browser workloads, connect an agent in managed mode and use its Catalog panel to stage capabilities as desired state.

What you want	Type	Typical Target	Typical Config
Copilot or AI chat	`copilot` or `ai`	`/home/alice/repo`	`mode=chat` or `command=copilot,mode=chat`
Browser shell	`terminal`	`/bin/bash`	leave blank
Web app	`http`	`http://localhost:3000`	leave blank
Command UI	`command`	`/usr/local/bin/deploy-check`	`timeout=120,cwd=/home/alice/repo`

The current single-tunnel runtime can execute http, command, tail, terminal, copilot, claude, codex, and generic ai with config.command. It stores tcp, grpc, shell, and watch for forward compatibility but currently reports them as unsupported.

API Key Management

Generate and manage API keys directly from the dashboard:

# From the dashboard UI:
# 1. Open Account → API keys
# 2. Enter an agent identity name (optional)
# 3. Click "Generate Key"
# 4. Copy the key: it is shown once

Fleet Tokens

Create fleet tokens with Kubernetes-style label selectors to grant access to groups of agents. Platform admins create them under Admin. The API behind it (POST /api/v1/dashboard/fleet-tokens, answering 201) takes a signed-in admin dashboard session; an API key is refused with 401.

Agents connecting with matching labels (--labels env=prod,region=us-east) are automatically authorized by the fleet token.

💡 MCP Integration

All dashboard functionality is also available through the MCP gateway, enabling AI-driven agent management and key rotation workflows.

Your fleet in the browser

Hub presence, machines, managed capabilities, terminals, and keys all live in one hosted console on nfltr.xyz.

Open Dashboard Sign up Getting Started Agent Orchestration → Dashboard walkthrough → CLI Reference →