Nemo Status

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 | head -10

The /status response is JSON; parse services.ready, services.not_ready, controllers.healthy, and controllers.status before rendering the summary block.

2. Present one summary block. Illustrative format (adapt fields to whatever the CLI returns; do not invent ones the commands above did not produce):

NeMo Platform status

Platform:    running
Services:    <ready_count> ready, <not_ready_count> not ready
Controllers: healthy
Agents:      <count>
  <name1> active
  <name2> stopped
Providers:
  <name1> available
Models (10):
  <model1>
  <model2>

Use the actual counts and names. If a section is empty, say "none."

3. Offer drill-downs. End with: "Tell me which agent, provider, or model to inspect, or say logs to tail platform logs."

For drill-downs:

Verification

Status is itself a verification: the commands together prove the platform is reachable, platform services/controllers are healthy, the agents plugin is loaded (or not), the provider is registered, and at least one model has been discovered. If any command returns an error, surface it in the summary block rather than hiding it.

If verification fails

Gotchas

• Read-only means read-only. Never run create, delete, stop, or any state-changing command from this skill, even if the dashboard suggests something is broken. Route to setup or teardown for state changes.
• agents deployments list requires the agents plugin. If it returns "no such command", the user has not installed the agents plugin yet; note that explicitly rather than failing silently.
• .venv/bin/nemo services ls defaults to running instances only. Use .venv/bin/nemo services ls --all to see stopped instance directories that still have logs on disk. Remove them with .venv/bin/nemo services prune or .venv/bin/nemo services rm <scope>. For liveness, cross-check against lsof -iTCP:8080 -sTCP:LISTEN.
• Status is a snapshot. A model still discovering will show as missing. Re-run after 30 seconds if the user just finished setup.
• Use .venv/bin/nemo, not bare nemo. Bash sessions do not carry venv activation across calls.