The O11 Neo Assistant is a multi-environment AI assistant solution designed to analyze and summarize logs, diagnose problems, and assist developers in monitoring their OutSystems 11 (O11) environments directly from OutSystems Developer Cloud (ODC).

The solution is composed of three main applications that work together through REST APIs and secure authentication.

🧩 Architecture

Communication Flow

1. The user interacts with the Interface in ODC.

2. The Interface sends the request to the Agent.

3. The Agent communicates with the Probe in O11 through REST APIs.

4. The Probe fetches and returns environment data.

5. The Agent processes the data using the AI model and returns the response to the Interface.

The O11 Neo Assistant combines on-premises data access (via Probe) with cloud-based AI reasoning (via Agent and Interface).
Once configured, users can chat with the agent to analyze logs, detect issues, and gain insights from their O11 environment without leaving ODC.

⚙️ Setup Instructions1. Deploy the Applications

• Deploy the Probe module in your O11 environment.

• Deploy both the Agent and Interface modules in ODC.

2. Configure Authentication

To allow ODC to communicate securely with O11, create an integration user with the correct role.

Create the Integration User in O11

1. Go to the Users application in O11.

2. Create a new user (e.g., NeoAssistant).

3. Assign the role NeoAssistantIntegrationUser (from NeoAssistantAIAgentProbe) to this user.

   
   

   
   

   
   

4. Set a password for the user — this will be used by the ODC Agent.

Configure the Agent in ODC

1. Open the Agent application in ODC.

2. Locate the REST API configuration for the Probe.

3. Set the Base URL to your O11 Probe endpoint.

4. Configure the credentials:

   • Username: the integration user created in O11.

   • Password: the password defined for that user.

5. Test the connection to ensure it retrieves data successfully.

6. You might also want to change the AI Model your agent connects to, to have more control over the data and less limitations.

🧱 Module SummariesProbe (O11)

• Purpose: Exposes system and monitoring information from O11 to be consumed by the ODC Agent.

• Type: O11 Service App

• Key Features:

  • REST API endpoints for logs, timers, and service actions.

  • Role-based access control.

  • Secure integration via authentication user.

Agent (ODC)

• Purpose: Connects to the Probe, retrieves data, and uses the AI model to analyze and summarize environment insights.

• Type: ODC Agent App

• Key Features:

  • Handles communication between ODC and O11.

  • Executes AI prompts to analyze log data.

  • Supports memory storage for chat history.

  • Requires configuration of REST API and credentials.

Interface (ODC)

• Purpose: Provides the chat UI for users to interact with the AI Agent.

• Type: ODC Reactive Web App

• Key Features:

  • Chat interface with persistent history.

  • Supports file and image uploads.

  • Connects directly to the Agent service.

  • Configurable agent name and help messages.