Skip to content

Local and health

This page groups the commands used to bootstrap the default local stack and inspect its health.

setup local

Use setup local to configure the default local stack:

kbolt setup local

This writes local provider bindings, downloads the default local models, and starts managed llama-server processes for the embedder and reranker.

local

Use local to inspect and control the managed local services.

When a managed local inference request hits a transport failure, kbolt attempts one automatic restart of the affected managed service before returning the error and prints a short stderr notice while it does so. local status remains the direct way to inspect that managed stack.

Subcommands:

  • status
  • start
  • stop
  • enable

Examples:

kbolt local status
kbolt local start
kbolt local stop
kbolt local enable deep

doctor

Use doctor when you need a structured readiness check:

kbolt doctor

doctor is the first command to run when setup or search looks wrong.

status

Use status to inspect the index state, storage usage, and model readiness:

kbolt status

If you use multiple spaces, scope it explicitly:

kbolt --space work status

For automatic freshness state, use:

kbolt watch status

models list

Use models list to inspect the configured role bindings and whether each one is ready:

kbolt models list