Live Console

The Live Console is a page in the R1-MCP dashboard that keeps updating while you talk to Claude. A conversation is turn-based; a client’s signal is not. The console covers that gap — you watch a client’s events and metrics tick continuously in one window while you work the problem in another.

This is an Early Access feature: unlock Early Access, then enable it under Features in the dashboard. Open it at https://r1-mcp.lanpulse.com/console.

It’s driven by watches

The console shows watches — the same watches the webhooks feature uses. There are two ways to start one:

• Ask Claude. watch_client arms a watch on a client MAC. With the console feature enabled, that call also returns a consoleUrl — a deep link straight to the live window for that watch, which Claude will hand you.
• Add it on the page. Enter a client MAC in the console itself.

There is deliberately no separate “console” tool. watch_client is the single registration point; enabling the feature is what makes it hand back the link.

A watch Claude starts while the page is already open is pulled into the list without a refresh.

What each watch shows

An event feed, newest first, of the webhook events mentioning that client, pushed the moment they’re ingested. This is the near-realtime half.

Three sparklines — RSSI in dBm, SNR in dB, and Tx in Mbps — built from polled R1 metrics. These are labelled as roughly three minutes delayed, because that’s the API’s own latency, not the page’s.

Note

Events carry their own RSSI in RUCKUS-positive relative units, which is a different scale from the dBm sparkline. The console shows it as feed text and deliberately never plots the two together — a rising number in the feed and a rising line on the chart do not mean the same thing.

The page stops polling R1 while the browser tab is hidden, so leaving it open in a background tab doesn’t keep generating API calls. Events keep streaming regardless.

What it needs to show anything

The event feed is fed by the webhooks receiver. If you haven’t configured RUCKUS One to deliver events to your receiver URL, the sparklines will still fill in from the API but the feed stays empty.

Using it with Claude

The pattern this exists for:

1. Ask Claude to arm a watch on the client you’re investigating.
2. Open the consoleUrl it gives you.
3. Go reproduce the fault, watching the feed and the signal charts live.
4. Come back to Claude and ask what was caught — the same watch data is available to the analytics tools.

See also

• Webhooks and analytics — the watch tools and the event receiver
• Workflow prompts — Live reproduce-and-catch does this as a guided workflow
• Features and feature flags — unlocking Early Access