Checking a running daemon
overcast status, wait, services and config: is the daemon up, is it ready yet, which services are enabled, and what configuration did it actually resolve.
Four read-only commands against --endpoint: status for a one-line answer,
wait for a script that has to block, services for what is enabled, and
config for what the daemon resolved.
overcast status
overcast wait --timeout 30sPart of the CLI reference.
overcast status
Pings /_overcast/health and prints one line — reachability, version, storage
backend. When the local instance registry is not empty it also prints a table
of every instance overcast start knows about —
name, backend, endpoint and lifecycle state — whichever one --endpoint
pointed at.
overcast status
overcast status --endpoint http://localhost:4570overcast wait
Blocks until the daemon at --endpoint reports healthy, then exits 0. This is
what a CI job runs after starting overcast serve in the background, before
the first AWS call; status checks once and returns.
| Flag | Default | Description |
|---|---|---|
--timeout | 60s | Give up waiting after this long. |
--interval | 500ms | How often to poll the health endpoint. |
--quiet | false | Print nothing on success. |
overcast wait --timeout 30sovercast services
Lists the AWS services the daemon has enabled and the runtime emulation tier of each — full, partial, inert or stub, explained in Reference index § Runtime emulation tiers.
| Flag | Default | Description |
|---|---|---|
--output | text | text (aligned table) or json. |
overcast services
overcast services --output json | jq '.services[] | select(.tier=="stub")'overcast config
Prints the running daemon’s effective configuration.
Important
The daemon has to have been started with OVERCAST_DEBUG=true. Without it
the command returns an error naming the variable rather than a bare 404.
| Flag | Default | Description |
|---|---|---|
--output | pretty | pretty (indented) or json (exactly what the daemon sent). |
OVERCAST_DEBUG=true overcast serve &
overcast configRelated
- Running the daemon —
serve,start,stop,restart,logs - Debug endpoints — the HTTP surface these commands read
- Environment variable reference — what
overcast configis showing you