ruview-live

Reviewed at commit 4a47292

RuView live sensing in Claude Code: /ruview opens a pane beside the transcript with three views: an overview of your CSI nodes (ESP32, Realtek) and 60 GHz…

Made by
ruvnet
What we checked

Typing /ruview opens a pane beside the conversation that shows your WiFi sensing nodes (ESP32, Realtek) and, if you set one up, a 60 GHz radar kit on your home network: packet rates, signal strength, presence, distance and the heart and breathing rates the device reports, plus a live waterfall and radar view. While the pane is open it starts the RuView command-line tool every few seconds to listen for sensor packets and read the radar. It does not see your prompts or Claude's work, reads none of your files, sends nothing to the internet, and keeps readings in memory only.

Review details

Static review of the source at the pinned commit; not run. hooks/hooks.json loads hooks/register.mjs, which imports model.mjs, anim.mjs, views.mjs and raster.mjs (pure drawing and parsing, no engine or Node calls). Hooks: session.start (registers the /ruview command via $.command.register), command.run for /ruview with off, refresh, overview, waterfall and radar, ui.render for its own Pane, ui.close and session.end (stop timers). Runtime calls: $.process.run, $.clock.every, $.clock.now, $.ui.open, $.ui.close, $.ui.status, $.ui.invalidate, $.ui.blit and $.ui.resolve. The only program it runs is node <pluginRoot>/../bin/cli.js with fixed argv: esp32 --seconds N --udp-port P --json [--spectrum ...] and, only when radarHost is set, mmwave --source esphome --host H --seconds N --json. Settings are clamped (port 1024-65535, capture 1-10 s, refresh at least 5 s) and radarHost must match a hostname/IP regex, so no shell or argument injection. The CLI (harness/ruview/bin/cli.js and the src/ modules it uses) was followed: esp32 binds a UDP socket on 0.0.0.0 at the chosen port for the capture window, receives and parses packets, and sends nothing. mmwave/esphome resolves the host, refuses anything that is not a private, loopback, link-local or CGNAT address, opens TCP 6053 and uses the ESPHome native API read-only, and gives up on password or encrypted APIs. Other CLI modules (flash, training, remote SSH) are imported but never called by this mod and run nothing at load time. CLI failures turn into an alert in the pane. Readings, history and the waterfall stay in memory, and nothing is persisted. The CLI lives outside the plugin folder, so after a marketplace install of only the mod folder it is likely missing and the pane shows only errors; it works as described when loaded from the @ruvnet/ruview npm package with Node on PATH.

What it uses
  • Reads your prompts: no
  • Sees tool calls: no
  • Blocks or changes tool calls: no
  • Reads or writes files: no
  • Runs programs on your machine: yes
  • Calls the model (uses tokens): no
  • Sends data over the network: yes
  • Stores data: no
  • Shows something on screen: yes
Hooked events
Screenshot of ruview-live

RuView live sensing in Claude Code: /ruview opens a pane beside the transcript with three views: an overview of your CSI nodes (ESP32, Realtek) and 60 GHz radar (rates, loss, RSSI, presence, device-reported vitals, alerts), a live CSI amplitude waterfall, and a radar range fan with vitals charts, all drawn in terminal cells. Reads only; runs the @ruvnet/ruview CLI it ships beside.

Made this mod? Add a badge to your README

modsforClaude badge for ruview-live

Paste this into your README. The badge says reviewed once the current version has been reviewed, and links readers to this page.

[![Listed on modsforClaude](https://modsforclaude.com/badge/ruview-live.svg)](https://modsforclaude.com/mods/ruview-live/)

← All mods