Diagnostics & Logs

Good diagnostics shorten support time dramatically. Before escalating an issue, gather the exact commands you ran, the current provider and MCP setup, and any health or config output you can reproduce.

Start with structured checks

gestura config check
gestura-app --health
gestura-app --test-audio
gestura-app --test-mcp

What information is most useful

Which command or UI workflow failed.
Your operating system and install path.
The provider you are using for language and voice features.
Whether the issue happens with all tasks or only one MCP-dependent workflow.

Developer and debug signals

Gestura can log more detail when developer mode or verbose BLE logging is enabled. Use those only when actively diagnosing a problem, because they increase log volume and may expose internal details you do not need during normal use.

Before you contact support

Reduce the issue to the smallest reproducible sequence.
Copy any exact error text.
Note whether the same issue happens in both GUI and CLI.

← Common Problems

Workflow Recovery →