jawb status

Checks whether the daemon is reachable and reports its state.

$ jawb status
daemon: ok (jawbd 0.1.1, api 15)
profile: default
tabs: 0
vault: windows-dpapi (current user)
bridge: enabled, compat-bridge/chromiumoxide (C:\Program Files\Google\Chrome\Application\chrome.exe)
purchase: gate approve, detection strict
approval: assurance verified-if-available, verifier Windows Hello, channels desktop,prompt,terminal
config: <data_dir>\config.toml
data dir: <data_dir>

• daemon: is the jawbd version and its API level. The CLI checks the API level before using a newer feature and refuses an older daemon with E_VERSION_MISMATCH.
• vault: names the master-key store in use: the OS credential store (Windows DPAPI, macOS Keychain, Linux Secret Service), or keyfile <path> when jawbd runs with --vault-keyfile (status then also warns W_VAULT_KEYFILE).
• bridge: is the compatibility bridge and the Chrome/Chromium it drives, enabled, but no Chrome/Chromium found, or disabled (compatibility_bridge.enabled=false) when jawbd runs with --no-bridge.
• purchase: and approval: are the effective purchase gate and approval settings. verifier is Windows Hello on Windows and none available where the OS has no verifier (macOS and Linux today).
• config: is the configuration file path. It exists only after the first change.

While a weakening setting change waits for a human, status says so before the report, and the effective values stay at their defaults:

$ jawb status
warning: W_CONFIG_UNCONFIRMED: purchase.gate weaker than the default and still at the default until a human approves `jawb confirm pc_fatgh8hmy339`
daemon: ok (jawbd 0.1.1, api 15)
...
purchase: gate approve, detection strict

If the daemon isn't running and auto-start is off (--no-autostart, JAWB_NO_AUTOSTART=1, or a non-default --daemon address), it tells you how to start it rather than failing silently, and exits 3:

$ jawb status
error: jawbd is not reachable at http://127.0.0.1:4180 (E_DAEMON_UNREACHABLE)
hint: start it with `jawb daemon start` (or run `jawbd` yourself), then retry

--json:

$ jawb --json status
{"command":"status","executor":"daemon","ok":true,"result":{"api":"v1","api_level":15,"approval":{"assurance":"verified-if-available","channels":["desktop","prompt","terminal"],"desktop_present":false,"verifier":"windows-hello","verifier_available":true},"compatibility_bridge":{"adapter":"compat-bridge/chromiumoxide","available":true,"chromiumoxide":"0.9.1","enabled":true,"executable":"C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe","headless":true},"config":{"path":"<data_dir>\\config.toml","pending":null,"unconfirmed":[]},"current_profile":"default","data_dir":"<data_dir>","id_retention_ms":30000,"pid":35736,"purchase":{"detection":"strict","gate":"approve"},"sessions":[],"tabs":0,"vault":{"available":true,"store":"windows-dpapi (current user)"},"version":"0.1.1"},"timing":{"daemon_ms":0,"total_ms":3},"trace_id":"tr_01m46nc1yn3tdbeyh0","v":1,"warnings":[]}

api is the path version (/v1); api_level is the feature level the CLI checks. pid is the daemon's process ID.

jawb version reports the same versions without needing a daemon:

$ jawb version
jawb 0.1.1 (x86_64-pc-windows-msvc)
built for jawbd 0.1.1 (api 15)
daemon: jawbd 0.1.1 running on http://127.0.0.1:4180 (api 15)