Health

Check server status and availability.

Bridge Mode

terminal
curl http://localhost:9867/health# Response: {"status":"ok","tabs":1}
Response
# CLI Alternative (human-readable by default)
pinchtab health
# Output: ok

pinchtab health --json              # Full JSON response

Bridge-mode health may also include:

  • crashLogs
  • failures
  • crashes

In error cases it returns 503 with status: "error" and a reason.

Server Mode (Dashboard)

In full server mode, /health returns the dashboard health envelope:

terminal
curl http://localhost:9867/health
curl http://localhost:9867/health
Response
{
  "status": "ok",
  "mode": "dashboard",
  "version": "0.8.0",
  "uptime": 12345,
  "authRequired": true,
  "profiles": 1,
  "instances": 1,
  "defaultInstance": {
    "id": "inst_abc12345",
    "status": "running"
  },
  "agents": 0,
  "restartRequired": false
}
FieldDescription
statusok when server is healthy
modedashboard in server mode
versionPinchTab version
uptimeMilliseconds since server start
authRequiredtrue when a server token is configured
profilesNumber of configured profiles
instancesNumber of managed instances
defaultInstanceFirst managed instance info, when present
agentsConnected agent count
restartRequiredtrue when file-based config changes need restart
restartReasonsRestart reason list when required

Notes:

  • defaultInstance is present when at least one instance exists
  • use defaultInstance.status == "running" when you want to confirm Chrome is ready
  • strategies such as always-on can create an instance automatically at startup