CLI Workflows

Once the basics are working, the CLI becomes a reliable way to repeat the same workflow with less friction. Think in terms of small sequences you can trust.

Common CLI workflow patterns

• Setup flow: init → edit config → config check.
• Voice flow: listen → speak task → inspect output.
• Chat flow: chat → iterate on a task with precise text input.
• Tool flow: add MCP server → verify status → run a real task that uses it.

When the CLI is better than the GUI

• You are already inside a project terminal.
• You want copy-pasteable commands for setup or troubleshooting.
• You need exact feedback from validation commands.
• You are documenting or automating your Gestura environment.

Keeping CLI workflows clean

• Run commands from the project you actually want Gestura to understand.
• Use project-scoped MCP tools whenever possible.
• Keep one terminal history thread per major debugging effort.
• Re-run config and health checks after significant changes.