doctor

strata doctor reports what this machine has: which binary is on the path, where the home directory resolved to, whether inference can run, and anything it considers an issue.

strata doctor

binary 1.2.5 database - home /home/you/.strata inference local_execution false models_catalogued 11 models_dir /home/you/.strata/models models_downloaded 0 ready_providers openai issues - path_ok true platform linux-x86_64 user_config path /home/you/.config/strata/config.toml state readable

Reading it

database is - because no database was named. Name one and it reports that database's health alongside the installation:

strata ./my-db doctor

database exists true info branch_count 1 created false default_branch default durable true memory_budget source derived_from_host total_bytes 6846744576 usable_host_bytes 27386978304 open true space_count 1 target durable_local version 1.2.5 open_ok true path /home/you/my-db

open_ok is the one to read when a database will not open: it separates "the path is not there" from "the path is there and something is wrong with it". version is the engine that wrote the database, which is not necessarily the binary you are holding.

path_ok answers the question behind most installation problems: is the binary you just ran the one on your PATH. A false here usually means a second copy earlier in the path.

issues is the field to read first. When it is - there is nothing to report; anything listed there is what to fix.

The inference block

This is the part that answers "why can I not generate anything". local_execution says whether this build can run a model on the machine at all, which depends on how the binary was built, not on what is installed. models_downloaded is how many local models are actually present, as distinct from models_catalogued, which is how many the build knows how to fetch.

ready_providers lists cloud providers considered usable. Read it as a key is present, not as a key works: a provider appears here on the strength of configuration alone, and a key that is expired or wrong still shows as ready. Tracked as strata-core issue 3408.

Configuration

user_config reports the file's path and its state, so a configuration that is not being picked up can be diagnosed without guessing where the file should have been. state distinguishes a file that is readable from one that is missing or unreadable.

Scripting it

--json returns the same facts as one document, which is the form to check in a setup script or a container build. The fields are the same; nesting matches the blocks above.

strata --json doctor

doctor reports. It does not repair anything, and it does not change the installation, so it is safe to run anywhere, including against a database another process is hosting.