Gestura.appgestura.app

User documentation

First Launch & Permissions

The first launch is where you turn a fresh install into a reliable daily tool. Your goal is simple: confirm the app can hear you, confirm it can use the providers or tools you want, and make sure the trust settings match your comfort level.

Before you begin

  • Make sure your preferred microphone is connected and visible to the operating system.
  • Decide whether you want fully local voice processing or a cloud speech provider.
  • If you plan to use MCP tools, have at least one tool server ready to add later.
  • If you use Haptic Harmony, make sure Bluetooth and any simulator settings are ready.

Permissions you may be asked about

  • Microphone: required for voice input and wake-word or hotkey-driven listening.
  • Notifications: useful if you want completion alerts while working elsewhere.
  • Keychain / secure storage: used to store sensitive provider secrets after migration from config.
  • Bluetooth: only relevant if you use a Haptic Harmony ring or simulator workflow.

Your first-launch checklist

  1. Open Gestura.app and allow microphone access.
  2. Confirm the selected input device is correct.
  3. Pick the interaction style you want most often: wake word, hotkey, chat, or a mix.
  4. Review the default permission level so you know when approvals will appear.
  5. Check whether you want sound notifications, haptic feedback, or automatic re-listening after feedback.
  6. If you use external providers, verify the required API keys or endpoints are configured.

What a healthy first run looks like

A good first run means the app can hear you, respond to a simple request, and show or speak back a clear result. If you are working from the CLI, the equivalent signal is a successful gestura init, a valid config check, and a working gestura listen or gestura chat command.

If something feels wrong

  • No response? Double-check microphone permissions and the configured audio device.
  • Unexpected approval prompts? Review the current permission defaults.
  • Provider issues? Confirm keys, endpoints, and fallback model settings.
  • Ring issues? Start with Haptic Harmony Ring and Ring Troubleshooting.

Next step

When the basics are working, move directly into the First Workflow Quickstart so you can validate Gestura with a real task, not just a settings screen.

© 2026 Gestura AI LLC. All rights reserved.