GUI Tour
The desktop app is the best place to understand what Gestura is doing in real time. Even if you mostly use the CLI, the GUI helps you learn the interaction model, watch approvals, and tune behavior visually.
The four surfaces most users rely on
- Listening controls: where you start, stop, or confirm voice input behavior.
- Conversation or task area: where prompts, replies, tool output, and follow-ups appear.
- Status and approvals: where Gestura reports progress and asks for permission on sensitive actions.
- Settings: where you tune voice, models, notifications, permissions, and integrations.
How to navigate confidently
- Start by checking whether the app is actively listening, idle, or waiting for you.
- Watch for approval prompts before assuming a workflow is stuck.
- Use the settings area for durable changes and the current conversation for task-specific requests.
- If you need exact troubleshooting, drop to the CLI for diagnostics and config checks.
What to look for on day one
- Your selected microphone and voice mode.
- The default permission level and whether approvals are expected.
- Any connected MCP servers or tool integrations.
- Notification or haptic settings so you notice workflow completion.
How GUI and CLI work together
Use the GUI to understand active work and to respond quickly to prompts. Use the CLI when you want to initialize config, add MCP servers, validate settings, or gather diagnostics. The two surfaces should reinforce each other, not compete.