fluid doctor
Run built-in health checks for the CLI and local environment.
Syntax
fluid doctor
Key options
| Option | Description |
|---|---|
--scope {authoring|pipeline|ingestion|infra|catalog|all} | Restrict checks to one scope (or run them all). Default authoring. |
--out-dir | Output directory for diagnostics |
--features-only | Only check FLUID feature availability |
--extended, --comprehensive | Run optional extended diagnostics |
--json | Emit per-check JSON (stable shape for CI) |
--verbose, -v | Detailed output |
Examples
fluid doctor
fluid doctor --verbose
fluid doctor --extended
fluid doctor --features-only
fluid doctor --scope ingestion # check the 6 acquisition engines
fluid doctor --scope all --json # CI-friendly full report
--scope — what each scope checks
Available in 0.8.3
The --scope flag is part of the 0.8.3 release. Earlier releases ran the equivalent of --scope authoring only.
| Scope | What it checks |
|---|---|
authoring | Forge copilot readiness — LLM provider configured, models reachable, tool-use capability |
pipeline | 11-stage pipeline capability — bundle, plan, apply work end-to-end on a fixture |
ingestion | The six acquisition engines — duckdb, dlt, meltano, airbyte, kafka-connect, debezium are importable; optional extras flagged |
infra | Infrastructure readiness — cloud creds, Kubernetes API reachable, provider CLIs on PATH |
catalog | Catalog connectivity — DataHub, OpenMetadata, Unity, Glue, Snowflake Horizon, Data Mesh Manager — only checks the ones declared in any contract under cwd |
all | Run every scope in sequence |
Per-check output is the same five-field shape (Typed CLI Errors) — name, severity, detail, fix hint, doc URL. The full-scope run still completes in under 3 seconds even on a fresh laptop.
Notes
- In
0.8.3, the default doctor experience is self-contained. Use--extendedwhen you explicitly want the optional workspace diagnostics path.