Smart Search CLI

Use the local smart-search command as the default execution layer for web research. This entrypoint keeps only routing, boundaries, and reference selection; load the focused reference file when command details or provider contracts matter.

Default Workflow

1. Run smart-search doctor --format json when configuration or availability is uncertain.
2. If doctor reports missing configuration, use smart-search setup or smart-search config set KEY VALUE when the user provides keys. Do not ask users to edit global environment variables by default.
3. If OpenAI-compatible search hangs or times out after doctor succeeds, run smart-search diagnose openai-compatible --format markdown and use its summary.
4. If doctor returns ok: true, use only smart-search CLI subcommands for web research. Do not call Codex native web search in the same task.
5. Use smart-search skills status --targets codex --format json when the installed global skill may be stale; use smart-search skills update --targets codex --format json to refresh it without rerunning setup.
6. Use smart-search smoke --mock --format json after CLI/provider architecture changes. Use --live only when real keys are available and the user expects live checks.
7. Preserve command lines and source URLs in your answer. Prefer citing fetched pages or primary_sources; treat extra_sources as follow-up candidates until fetched.

Routing