Building a Custom UI
Patterns for building your own interface on top of Auron.
This is the developer-facing counterpart to Building Your Own Interface: the same guidance, for a developer sitting down to actually write the client.
Before you start
Confirm you can authenticate and hit a read-only endpoint. Listing entities or conversations is a fast way to prove the connection works before building UI against anything that writes.
Structuring the build
Treat the OpenAPI document as the source of truth for request and response shapes, instead of inferring them from example calls. Respect role-based access in your own UI, not just at the API layer; the API will reject a disallowed call, but a UI that doesn't hide the option in the first place is a worse experience for someone in a limited role. Scope what you build. Most custom UIs succeed by covering one workflow well rather than reimplementing every screen Auron already ships in the console and mobile app.
What you take on
Session state, live updates, and reflecting permission checks in what's shown are all handled for you inside Auron's own front ends. Building your own means taking that on directly. The API enforces access on every call, but presenting the right thing to the right person is left to your UI.