nemo-status

name	nemo-status
description	Read-only dashboard for NeMo Platform. Combines platform health, deployed agents, registered providers, and available models into a single view. Use over generic status checks for any NeMo Platform dashboard request.
triggers	["platform status","what is running on nemo","how is the platform","show me nemo health","nemo status","check the platform","nemo dashboard"]
not-for	["nemo-setup (use to install or start the platform)","nemo-teardown (use to stop the platform)","nemo-try-agent (use to send a query to a deployed agent)","nemo-skill-selection (use for dispatch when intent is unclear)"]
preconditions	["nemo_cli_available"]
compatibility	nemo-platform >= 0.1.0; read-only CLI calls only; no state changes; safe under any sandbox (requires `lsof`, `curl`, and a venv with the `nemo` binary — no Docker); works whether or not the agents plugin is installed (degrades gracefully).
maturity	active
license	Apache-2.0
user-invocable	true
allowed-tools	["Bash","Read"]

NeMo Platform status

Single dashboard view of the running platform. Read-only. Never modifies state.

Pre-flight

Confirm the CLI is installed. If .venv/bin/nemo is missing, route to nemo-setup and stop:

[ -x .venv/bin/nemo ] && echo "CLI_OK" || echo "CLI_MISSING"

What you do

1. Check platform up-status first; gate everything else on it. Use a two-step probe — lsof for ground truth, then curl for a functional check. If either fails, report "platform down," suggest nemo-setup, and stop. Do not run the other three commands.

# Ground truth: anything listening on :8080?
lsof -iTCP:8080 -sTCP:LISTEN >/dev/null 2>&1 || { echo "PLATFORM_DOWN (nothing on :8080)"; exit 1; }

# Functional check: platform readiness endpoint answers?
HTTP=$(curl -sS --connect-timeout 2 --max-time 5 http://localhost:8080/health/ready -o /dev/null -w "%{http_code}" 2>/dev/null || echo "no-response")
case "$HTTP" in
  200) echo "PLATFORM_UP (HTTP $HTTP)" ;;
  *)   echo "PLATFORM_WEDGED (listener present, /health/ready returned $HTTP)"; exit 1 ;;
esac

Do NOT use nemo services status or nemo services ls for this check. Both report stale "running" state from a held instance lock after the underlying process has died. lsof is ground truth.

Only if both probes pass, run the remaining commands to capture the other dashboard rows:

curl -fsS --connect-timeout 2 --max-time 5 http://localhost:8080/status
.venv/bin/nemo agents deployments list 2>/dev/null
.venv/bin/nemo inference providers list
.venv/bin/nemo models list |  -10