Workflows & Approvals
A workflow is the chain between your request and the finished result. In Gestura, that chain can include interpretation, planning, tool use, MCP access, feedback events, and approval checkpoints.
The standard workflow loop
- You ask for something.
- Gestura decides what information, knowledge, memory, or tools are required.
- It asks for approval if the next step is sensitive.
- It runs the action and reports progress.
- If reflection is enabled and the turn was weak, it can add a correction stage before the final answer.
- You review the result, accept it, or continue with a follow-up.
Approval levels in practice
The default permission level determines how often Gestura pauses. In safer modes, reading and analysis can happen freely while actions with side effects require confirmation. In more open modes, Gestura can act more autonomously. Pick the level that matches the environment you are working in.
What makes a workflow reliable
- Clear instructions at the start of the task.
- The right knowledge or prior memory being available when the task needs it.
- Known tool availability and healthy MCP connections.
- Permission defaults that match the sensitivity of your work.
- Good feedback settings so you notice completion, errors, or follow-up prompts.
Where workflows can fail
- Missing permissions.
- Missing or mismatched knowledge for the job.
- Disconnected MCP servers.
- Incorrect provider configuration.
- Ambiguous prompts or stale session context.
Advanced workflow features
Gestura also supports more advanced behavior such as ERL-inspired reflection, event-driven automations, hooks, tool feedback, and agent-to-agent delegation when those features are enabled. Treat those as power-user features: add them only after your baseline workflow is already predictable.