The browser submits a bounded ticket action to its own server. The server authenticates the user, checks the ticket and selects an allowed agent/model configuration. Provider keys and OCI request signing stay on that server. A SaaS preview cannot call a private laptop loopback address. The local reference is a loopback workshop server, not a production login or tenant boundary.
Start with the job and the messages it needs. Register narrow tool schemas and reviewed handlers. Add the loop that accepts a model proposal, validates its arguments, executes the handler and appends the observation for the next model call. Add authorization, budgets and metadata spans around those steps.
The local Studio shows native tool calls; the existing hosted sample uses a LangGraph coordinator and JSON protocol. A framework can organize the flow, but your code still defines ownership, stopping conditions, safe tools and evidence. Matching HTTP paths or changing a URL does not make two different APIs compatible.
Choose a component to connect the idea with its real source boundary.
Create a synthetic ticket, search for it, open its detail and run a real investigation. The answer must come from your configured model and permitted tool. A static preview is only a sketch.
Your app has a usable inbox, a connected AI action and clear loading/failure states. Keep its limited in-memory lifetime explicit. Durable persistence and production authentication are separate capabilities.
Keep the local runtime receipt, but do not spend this build hour provisioning telemetry systems. Part 4 adds the full trace/export/readback workflow to this same app.