reticle status

Ask whether the Reticle daemon is up and which app sessions have connected to it.

reticle status is the command that tells you whether the install actually finished. Not a tick in a checklist: a connected app.

npx @reticlehq/server status [--port N]

Flags

Flag	Type	Default	What it does
--port N	number	4400 (or RETICLE_PORT, or the port in .reticle.json)	Which daemon to ask

What it prints

One JSON line on stdout. Real capture, daemon up and no app connected:

{
  "t": "2026-08-14T19:38:37.737Z",
  "event": "reticle_status",
  "port": 4400,
  "running": true,
  "pid": 4795,
  "sessionCount": 0,
  "sessions": [],
  "why": "no browser session connected. Two things to weigh, and neither of them is proof. (1) Nothing is listening on the ports Reticle scans ... (2) There is no `.reticle.json` in the directory this daemon is running in ..."
}

Field	Meaning
running	Whether a usable daemon owns the port
presence	Present when the pid file is dead: daemon, foreign, or absent. The port is asked, not just the pid file
pid	The daemon process
sessionCount / sessions	Connected app sessions, each with sessionId, url, throttled, stale
why	Present when zero sessions connected. Names the two likely causes and refuses to assert either
updateAvailable	Present when a newer server version is on the registry

status asks the port, not only the pid file. running: false used to be printed about a port that was demonstrably occupied, which sent the reader off to start a daemon that could never bind.

Exit codes

Always 0. This command answers a question; it does not judge the answer.

Worked example

npx @reticlehq/server init
npx @reticlehq/server status    # a session in the list means the app is genuinely wired

Nothing connected?

The bridge port is not your dev server port, and that is the most common cause.