Skip to main content
command CX Codex

ping — Claude Code command: what it does, how to install

ping is a Claude Code command that checks the local Agent Monitor dashboard API and reports its reachability.

MIT ★ 1,198 updated 2026-10-23

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor
/plugin install ccam-dashboard@claude-code-agent-monitor-plugins
Open on GitHub

What ping does

The command runs a curl request against http://localhost:4820/api/stats with a 5-second timeout. It checks the HTTP status code and total round-trip time. It does not modify project data.

Output stays limited to a single line without commentary. On receiving a 2xx HTTP code, it prints an UP status alongside latency in seconds or milliseconds. If curl fails due to a timeout, connection refusal, or an error status code, it prints DOWN and reminds you to launch the server with npm start or npm run dev from the repository root.

Without curl installed and the dashboard active on port 4820, the probe fails immediately.

What it helps with

  • check Agent Monitor dashboard API reachability
  • measure response latency for http://localhost:4820/api/stats
  • verify local monitor availability in a single line

Example prompts for the agent

  • /ping
  • Check if the agent monitor dashboard is running

How to install ping

1Plugin marketplace

/plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor
/plugin install ccam-dashboard@claude-code-agent-monitor-plugins

2Manually: put the files in place

.claude/commands/ping.md

Call it with /ping. For all projects use ~/.claude/commands/

Questions about ping

How to install ping in Claude Code?

Run /plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor, then run /plugin install ccam-dashboard@claude-code-agent-monitor-plugins.

What does the ping command do?

It queries http://localhost:4820/api/stats via curl with a 5-second timeout and reports either UP or DOWN with response time.

What should I do when ping reports DOWN?

Start the dashboard server from the root of the repository by running npm start or npm run dev.

Source text

ping.md · MIT
---
description: Check Agent Monitor reachability and print UP/DOWN with latency
---

Check whether the dashboard API is reachable and report latency.

Run:

```bash
curl -s -o /dev/null -m 5 -w '%{http_code} %{time_total}s' http://localhost:4820/api/stats
```

`%{http_code}` is the HTTP status and `%{time_total}` is the total round-trip
time in seconds.

Print one line:

- If the request succeeds with a 2xx status:
  ```
  ✅ UP | http://localhost:4820/api/stats | 200 | 0.042s
  ```
  (use the real status code and the real latency, converting seconds to ms if
  clearer, e.g. `42ms`).

- If `curl` exits non-zero (connection refused/timeout) or the status is not 2xx:
  ```
  ❌ DOWN | http://localhost:4820/api/stats unreachable — start it with `npm start` (or `npm run dev`) from the repo root
  ```

Output only the single line — no preamble. Do not modify any data.

© Son Nguyen · MIT · hoangsonww/Claude-Code-Agent-Monitor

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set155

The whole set →
file-headers file-headers makes each source file open with a short, honest overview plus the exact line @author Son Nguyen <[email protected]>. CX Codex +1 ★ 1,198repo stars status Polls the local Claude Code Agent Monitor dashboard to print health status and session counts in a single line. CX Codex +1 ★ 1,198repo stars open-dashboard open-dashboard prints the Agent Monitor address and the commands to start or open it. Use it when you need the local dashboard instructions. CX Codex +1 ★ 1,198repo stars report-analyst report-analyst builds executive, cost, reliability and workflow reports from a local CCAM API, keeping units, scope and data freshness intact. Handy when a stakeholder summary has to hold up to scrutiny. CX Codex ★ 1,198repo stars repo-onboarding repo-onboarding maps a repository before coding, helping locate the right module, ownership, and checks for a planned change. CX Codex +1 ★ 1,198repo stars debug-live-issue debug-live-issue walks an agent through incident-style debugging: pin down the symptom, isolate the subsystem, reproduce, prove the cause, then apply a minimal fix. CX Codex +1 ★ 1,198repo stars overspend overspend spots the most expensive Claude Code sessions via a local dashboard and displays them in a ranking table. Useful when spending spikes unexpectedly. CX Codex +1 ★ 1,198repo stars top-spenders top-spenders sorts Claude Code sessions by cost and lists the most expensive ones. Use it to inspect session spending and compare the top entries with the total. CX Codex +1 ★ 1,198repo stars

Project sponsors

Companies that keep this analytics open