---
title: Stream Setup (wiring map)
description: The GET STARTED view at
---

# Stream Setup (wiring map)



## Purpose

STREAM SETUP is the console's first-run orientation page. It answers "what do I need to do to get cameras streaming, and what is the next step right now?" without reading any other documentation.

Deep link: `ops.useargus.co/#/wiring` (nav group GET STARTED).

## What it shows

* Four clickable stage cards in data-flow order, with labelled connectors: Camera, Streaming Agent (store PC), GPU Inference Pod, then Portal (Loss Prevention).
* A status pill on each stage: LIVE, WAITING, or UNKNOWN, derived from live data (`GET /compute/workers/served` for the pod and camera state, `GET /support/fleet` for the agent).
* A NEXT STEP banner that names the single next action: pod down points to "RESUME on COMPUTE"; pod up with no frames points to bringing up the agent; all stages live points to opening the portal Loss Prevention tab.
* Clicking a stage opens a detail panel: what the stage does in plain English plus numbered bring-up steps.

## Actions

This page is an explainer; it performs no mutations.

* Clicking a stage card opens its detail panel with bring-up steps.
* The GPU pod stage (and the NEXT STEP banner when the pod is down) shows a "Go to COMPUTE" button that navigates to [#/compute](/docs/console/compute).

## Matching CLI

There is no single argusctl command for this page; it is an orientation surface. The underlying data comes from:

```bash
argusctl compute served
argusctl support fleet
```

See [argusctl compute](/docs/cli/compute) and [argusctl support](/docs/cli/support).

## Notes

* The explainer and stage cards are built once per navigation; only the status pills and the NEXT STEP banner patch in place on the 15 second refresh tick.
* With no operator token set, the page still renders the full explainer: all pills read UNKNOWN and the banner tells you to set your token in Settings.
* Known caveat from the console audit: a backend 500 on this page can be mislabeled as the missing-token state.


---

For a semantic overview of all documentation, see [/sitemap.md](/sitemap.md)

For an index of all available documentation, see [/llms.txt](/llms.txt)

For agent-facing discovery, including API and MCP surfaces, see [/agents.md](/agents.md)