Operations

Server

any run is a plain foreground process: it loads config, boots the selected account's engine, binds a loopback listener and serves until it receives SIGINT/SIGTERM or POST /v1/shutdown. No daemonization — run it under a terminal, tmux, systemd --user or whatever supervisor you prefer.

Startup

1. Load config — file, then ANY_* environment overrides, then flags (Configuration).
2. Resolve the data-dir root (default ~/.any/) and pick the account:
   • auth.walletPath / --wallet → that wallet, data flat at the root (manual mode);
   • account: / ANY_ACCOUNT / --account → <root>/<id>/ if present, else the root wallet (its derived id must match);
   • no selector → the root wallet.key if one exists, else a sole <root>/<id>/ directory, else no account.
3. With an account, boot its engine before the listener binds, so boot failures surface immediately: pid lock in the account dir → open the wallet → derive the account id → open the SDK → open the search indexer. any run never generates a wallet; create accounts with any init or over HTTP.
4. Without an account, start unauthorized. Every /v1 route except /v1/health, /v1/shutdown, /v1/openapi.json and /v1/auth returns 401 auth.required until POST /v1/auth creates, restores or selects an account and boots the engine in place — no restart. See Accounts.
5. Bind 127.0.0.1:<port> (default 7001) and serve.

any run --data-dir ~/.any --addr 127.0.0.1:7001 --log-level info

Opening the SDK also starts the one-to-one inbox notifier when a coordinator is configured, so incoming direct-space requests surface as pending rows in the space list without any wiring (One-to-one spaces).

The boot pass

The SDK returns from Open after local wiring only. Eager space loading and offline catch-up run on one serial background pass, so the server serves as soon as the listener binds; until a space's turn comes, reads against it return the pre-offline state.

GET /v1/health reports the pass:

{ "status": "ok", "version": "any v0.1.0 (sdk v0.0.0)",
  "startedAt": "2026-04-23T18:12:00Z", "account": "A3…",
  "bootstrapping": true }

bootstrapping is true while the pass runs and false when it completes (or when the server is unauthorized). It reports the one-shot pass only — per-space convergence is on sync status. Health never needs SDK state, which makes it the right probe for supervisors and for any status.

Note. Boot also upserts this device's row in the account's devices registry (OS and version each boot, hostname as the name on first registration), and — for the well-known derived spaces the account already has — waits for their bundle registries to converge so a client ensuring right after a restore meets real state rather than an empty one.

Listen address

Shutdown

Two triggers, one path:

1. SIGINT / SIGTERM
2. POST /v1/shutdown (any stop)

The server stops accepting new requests, drains in-flight ones with a 10-second deadline, lets open SSE streams emit their terminal closed{reason: "server_shutdown"} frame, closes the SDK and exits 0. After the deadline, remaining requests are aborted and the process still exits 0.

any stop
# or
curl -s -X POST http://127.0.0.1:7001/v1/shutdown

Single-instance lock

When an account's engine boots, the server writes <account-dir>/server.pid (the root itself for the legacy flat layout). A lock held by a live PID fails the boot with a clear message — 409 auth.account_in_use when it happens through POST /v1/auth. Stale locks whose PID no longer exists are reclaimed.

The lock is per account: two servers may share one data-dir root as long as they serve different accounts on different ports. An unauthorized server holds no lock until it boots an account.

One server, one account

A process serves exactly one account for its lifetime. Switching the account of a running server is not supported — stop it and start with --account <id>, or let POST /v1/auth pick on an unauthorized server. Two accounts side by side:

ANY_ACCOUNT=A3… any run --addr 127.0.0.1:7001
ANY_ACCOUNT=B7… any run --addr 127.0.0.1:7002

Logging

All logging goes through one backend; the HTTP framework's logger is wired to the same stream. The log config block applies globally: default level info, colorized output to stderr, optional extra output paths (e.g. a file), optional JSON format. --log-level debug or ANY_LOG_LEVEL=debug raises verbosity for one run. See Debugging.

Background workers

None of them is on any request's critical path; each reports long work as a process.