CLI Diagnostics

When Gestura is not behaving the way you expect, the CLI is usually the fastest route to a trustworthy answer. It shows exactly what is healthy, what is misconfigured, and what to test next.

Start with config validation

gestura config check

Use this after editing config.yaml, changing providers, or adjusting advanced settings.

Use packaged health checks

gestura-app --health
gestura-app --test-audio
gestura-app --test-mcp

These checks help isolate whether the issue is with the app environment, microphone access, or MCP connectivity.

A simple diagnostic sequence

1. Check config validity.
2. Check app health.
3. Check audio input.
4. Check MCP status.
5. Retry the workflow with a smaller task.

When to escalate

If diagnostics are clean but the behavior is still clearly wrong, gather the output, note your current provider and MCP setup, and then use Support & Escalation.