Quickstart
Embed the agentic loop in your app
This quickstart is for developers who want to adopt Gestura's library model in their own product. The goal is to understand the architecture quickly, then use the generated API docs for exact implementation details.
Choose the application boundary
Decide where the loop should live: inside your desktop app, backend service, automation worker, or device-adjacent runtime. Start from the runtime you control best.
Start from the core facade
Use the stable core library surface first, then follow the owning domain crates only when you need deeper control. Generated Rustdoc should answer exact API questions.
Wire the loop before adding interfaces
Get request handling, tool execution, permissions, streaming, and iteration boundaries working before layering on voice, gestures, or product-specific UX.
Introduce gestures as structured events
Treat gestures and haptics as typed application signals. They should feed the same orchestration system as text, voice, and background events.
Validate with docs and simulation
Use Rustdoc for exact signatures, the simulator for interaction testing, and examples for composition patterns you can adapt to your own app.
The loop you are implementing
No matter what UI or transport you build around it, the reusable architecture is the same: collect intent, resolve context, call the model with tool affordances, execute approved actions, append results, and continue until the system can produce a final answer or next step.
input -> resolve context -> call model with tools -> inspect requested actions -> execute approved tools -> append tool results -> reflect / continue -> stream updates -> final response
Practical first milestones
- • Return one full loop response with no external tools.
- • Add one safe tool or capability and display its iteration boundary.
- • Capture loop state so users can understand what happened.
- • Introduce gesture or haptic events only after the base loop is observable.
- • Use simulation before depending on physical hardware for every test.
Where generated docs fit
Keep the human-written portal focused on architecture, learning flow, and practical adoption. Keep exact reference material close to the code via inline docs so cargo doc --workspace --no-deps remains authoritative.