An embedded AI agent helps a user complete a task inside an application. It needs the relevant page state, a defined set of actions and access checks enforced by your application. A chat window alone does not provide those capabilities.
For example, “show my overdue invoices” can open the invoices route and set a status filter. The application performs those operations through functions you register. This example describes an integration pattern, not an automatic right to read or change every screen.
Expose routes, state and functions separately
| Surface | What the agent receives | What your application controls |
|---|---|---|
| Navigation | Declared routes and their purpose | Router behavior and route guards |
| Page state | Selected filters, fields or page data | Which values can be read or changed |
| Business action | A named function and its parameters | Authorization, validation and execution |
Use the AGO SDK examples for React, Vue, Angular or plain TypeScript. Register only the context needed for the task. Reading the current filter is different from exposing an entire customer record.
Keep the existing permission checks
The agent’s request must pass the same server checks as a manual action. A browser function is an entry point, not proof of authorization. Never give a browser a privileged API key to bypass those checks.
For actions that require customer approval, ask for confirmation and make clear what will change. Choose the decision rule per action: the agent can act, the customer confirms, or a team member decides. A demonstration of a filter change does not establish that an agent should approve payments.
Wait for the destination page before continuing
Navigation changes the available context. If the agent opens an invoice and immediately asks for its details before loading completes, it can reason from the previous page. Return an action result and expose the new state after it becomes available.
The client functions documentation and SDK documentation explain how AGO connects registered functions to a conversation. Test route changes, rejected actions and stale data in your own application.
Make human handoff part of the task
A customer may need a person even after a successful action. Preserve what the agent changed, the customer’s goal and any unresolved question. The helpdesk should receive the context needed to continue.
For a broader support rollout, use the platform overview. For the product experience and supported use cases, see AGO Agents. These address different decisions from choosing a JavaScript integration.
Validate a small task before expanding
Start with a bounded task such as finding an invoice. Check that the agent opens the correct route, applies the permitted filter, handles an empty result and refuses another account’s data. Then add a state changing operation with the approval it requires.
Measure task completion separately from the number of messages or clicks.
