Skip to content
Gormes Docs

Smoke-test offline with doctor

Smoke-test offline with doctor

Section titled “Smoke-test offline with doctor”

Outcome: A passing local readiness check for runtime identity, secrets, TUI, and the built-in tool catalog — no network, no credentials.

Prerequisites: gormes installed on $PATH.

First-run proof order

Section titled “First-run proof order”

Use this sequence before credentials / before entering provider credentials:

Terminal window
gormes version
gormes doctor --offline
gormes setup

gormes doctor --offline is the canonical local proof step. It needs no pip, no venv, no Docker daemon, no network submit, and no provider credentials before the check passes.

Steps

Section titled “Steps”

  1. Run doctor in offline mode

    Terminal window
    gormes doctor --offline

    Lines beginning with [PASS] indicate healthy local subsystems. [SKIP] provider health is expected — it confirms the offline path skipped the network probe.

  2. Open the native TUI without provider calls (optional)

    Terminal window
    gormes --offline

    The Bubble Tea TUI opens with no provider health checks or network submits. Quit with Ctrl-C.

Verify

Section titled “Verify”
Terminal window
gormes doctor --offline

Expected output (truncated):

[PASS] SecretRef runtime: resolved=0 inactive=0 unavailable=0
[SKIP] provider health: skipped (--offline)
[PASS] Native TUI: available: Go-native Bubble Tea TUI compiled into gormes
[PASS] Toolbox: 35 tools registered (...)

If every non-[SKIP] line reads [PASS], the local runtime is healthy.

Troubleshooting

Section titled “Troubleshooting”
  • command not found → The binary is not on $PATH. Re-run the installer or follow install from source.
  • [WARN] build identity: dirty build → You are running a locally built binary with uncommitted source. Safe to ignore for smoke tests.
  • [FAIL] on any local subsystem → Run diagnose a broken install.

See also

Section titled “See also”