Troubleshooting

The plugin is not visible

Confirm the marketplace installation (codex plugin list / a Claude Code plugin listing shows strata19), then enable Strata19 in your host's plugin settings. Reinstall after a plugin release — both hosts cache an installed plugin by version, so a newer commit in the repository (or a locally rebuilt bundle) does not reach an already-installed copy. codex plugin add strata19@strata19 / claude plugin install strata19@strata19 pulls the new version into a fresh cache directory.

A GUI-launched host can't find `node`

Hosts that launch plugins from a GUI (rather than an inherited shell) sometimes start the plugin process with a stripped PATH that doesn't include your nvm/Homebrew node. The plugin's own launcher script hunts across common nvm and Homebrew install locations before giving up — if the plugin still fails to start, confirm node --version succeeds from a completely clean shell, not just your interactive one.

Strata19 inspected the wrong repository

Set STRATA19_PROJECT_ROOT to the absolute path of the project, or ask the agent to call strata19.initialize_project with the repository's absolute path. If a response's provenance names rootResolutionSource: "recovered" or "cwd", the server fell back past its normal resolution order — read the accompanying bindingWarning, which names the resolved root and why, before trusting that answer. This matters most when more than one repository is open on the same machine at once: recovery can name the wrong one.

Check, in order: the web app is actually running and reachable; STRATA19_WEB_BASE is set; that value is https://, not http:// — an https sandboxed iframe cannot frame http://localhost, independent of any CSP setting, and no browser flag changes this; and, for a local dev server specifically, that your host's origin is in Next's allowedDevOrigins. Each of these produces a different symptom (blocked/blank panel, an explained placeholder, a frame that silently never loads, or a frame stuck on "refreshing…") — matching the symptom to this list is faster than guessing.

Model assistance is unavailable

Free deterministic capabilities (verification, change-impact, implementation context, checkpoints, work-item capture without enrichment) work with no key configured at all. For BYOK-assisted output — work item enrichment, spec drafting, remediation explanations, recommendations, or query interpretation — configure OPENAI_API_KEY or STRATA19_MODEL_KEY, then confirm STRATA19_MODEL_MAX_CALLS hasn't been set to 0 and, for Specbook generation specifically, that STRATA19_SPECBOOK_BUDGET_USD isn't already exhausted.

A result is incomplete

Read the caveats and analyzed-coverage note rather than the pass/fail line alone. Incomplete evidence is an honest result, not a bug: a scan that hit an unsupported file type, an unresolved import, or a repository too large for the configured budget says so. Narrow the request, install any named local dependency, or inspect the supporting file-and-line evidence directly before assuming the tool is wrong.

A finding won't go away after a fix

A finding disappearing from a later verify_implementation run means it is absent from that comparison — not, by itself, proof the underlying problem is repaired. If the same class of issue keeps reappearing, check whether the fix addressed the specific evidence cited (file, line, detector) rather than a related but different instance of it.