CLI Quickstart

Use this path if you want to get productive from the terminal first. The goal is to create a working config, test a basic interaction, and make sure your environment is healthy enough for deeper workflows.

Step 1: Create the default config

gestura init

This creates the baseline configuration that later guides voice, providers, permissions, and MCP behavior.

Step 2: Start an interaction

gestura listen

gestura chat

Use listen when you want voice activation and chat when you want typed control.

Step 3: Validate config health

gestura config check

This is the fastest way to catch malformed config, invalid provider values, or settings that fall outside accepted ranges.

Step 4: Verify the packaged app surface if needed

gestura-app --version
gestura-app --health

These checks are especially useful after a fresh desktop installation or when you suspect an environment issue rather than a workflow issue.

Common next actions

• Add an MCP server with gestura mcp add ...
• Check tool connectivity with gestura mcp status
• Review config details in Configuration Reference