DOCS

Node Health

Check the local daemon without confusing retired TCP behavior for an outage.

Last reviewed: 2026-07-17. Product status: alpha.

[Docs index] [Install] [Apps] [Developer]

FAST HEALTH CHECK

curl -s --unix-socket ~/.lastdb/data/folddb.sock \
  http://localhost/health
# expect: {"status":"ok"}

If this succeeds, the local node is up.

STATUS

NODE

lastdb status

Shows host vitals and request activity.

APP READ

kanban list
brain ask "what did I decide recently?"

A successful socket-backed app read also proves the node is reachable.

COMMON CONFUSION

The legacy TCP endpoint on 127.0.0.1:9001 is retired. A connection failure there does not, by itself, mean LastDB is down.

Prefer the Unix socket path: ~/.lastdb/data/folddb.sock.

RESTART BOUNDARY

Restart only after the socket health check fails and ordinary app reads fail. Do not restart just because an old TCP-only command printed a :9001 error.

brew services restart lastdb

RELATED DOCS

Install

Install LastDB

Homebrew install, what ships, data directory, socket, and version checks.

Use

Daily Loop

Brain for durable context, Kanban for live work, MCP for agents.