Anatomy of an Agentic App

Here's an example of an Executive Advisor agentic app that consists of four agents.

Anatomy of an agentic app

Callout Number Name Description
1 Ask Oracle Advisor Lets you ask natural language questions against the set of agents included in the app.
2 Summary Section Displays the most critical information across all the domains in the app's agents. The summary is typically the first content users read when opening the app.
3 Agents The example agentic app includes four agents, each represented by a tile on the dashboard. An agent can provide its own headline to convey the most important information for the app user. Users can zoom in on any agent to keep focus on that agent. Any subsequent questions, actions, and communications are then scoped to the selected agent.
4 Widget A widget generated by an agent from the widget library. Each widget has space for the agent to provide its own insights, and capabilities that the user can choose from. Widgets can also have agent-specific actions that the user can act upon.
5 Priority Actions App-specific critical information that require the user's immediate attention and provide options for the user to take action.
6 Communications Outbound message suggestions that may be predefined by the app or generated by the LLM. It can start a flow allowing the user to construct the content and send the communication.