Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 0 additions & 12 deletions explore-analyze/ai-features/ai-agent-or-ai-assistant.md

This file was deleted.

Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
---
applies_to:
stack: preview 9.3
serverless: preview
products:
- id: kibana
- id: observability
- id: security
- id: cloud-serverless
---

# Compare AI Agent and AI Assistant

AI Agent is a technical preview chat experience designed to replace Elastic Assistant for {{observability}} & Search and Elastic Assistant for Security.
Copy link
Contributor

@leemthompo leemthompo Dec 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's leave the tech preview designations to the applies_to tags, they'll get jealous otherwise

designed to replace Elastic Assistant

I'm not sure if we want to message like this, AB is a much more powerful, general framework, and one offshoot is that we'll be replacing AI assistant functionality with stuff powered by AB, rather than saying it's designed to replace the assistant

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we will especially want to avoid this language in the tech preview release, because it won't be able to replace everything in assistant at this point.


AI Agent uses Elastic's [Agent Builder](/solutions/search/elastic-agent-builder.md) platform. It lets you design your own purpose-built agents and enables a more cohesive AI chat experience across all Elastic's products. You can create specific agents for use in different workflows, and give them precise access to the tools and data they need.

## Enable AI Agent

While AI Agent is in technical preview, you may have to opt in to enable it. This behavior varies by solution:

Check notice on line 20 in explore-analyze/ai-features/ai-chat-experiences/ai-agent-or-ai-assistant.md

View workflow job for this annotation

GitHub Actions / preview / vale

Elastic.WordChoice: Consider using 'can, might' instead of 'may', unless the term is in the UI.

- **{{observability}} and {{elastic-sec}}:** Each solution's classic AI Assistant remains the default chat experience.
- **{{es}}:** AI Agent is the default chat experience.

To enable AI Agent, use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md) to find [**GenAI Settings**](/explore-analyze/ai-features/manage-access-to-ai-assistant.md).

## Feature differences between AI Agent and AI Assistant

Some functionality supported by Elastic's AI Assistants is not supported by AI Agents. The differences vary by solution.

### AI Agent features in {{elastic-sec}}

AI Agent for {{elastic-sec}} provides a similar experience to AI Assistant for Security at a high level, but with a number of differences.

The following AI Assistant for Security features are not supported in AI Agent:

- **Knowledge Base**
- **Data anonymization**
- **Time awareness**
- **Chat sharing**
- **Citations**
- **Audit logging**
- **Quick prompts**

Also, AI Agent chats do not show previews of data you attach to a message, such as Alerts and Attacks.

### AI Agent features in Elastic {{observability}}

### AI Agent features in {{es}}
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,7 @@ The **GenAI Settings** page has the following settings:
- If **Elastic Managed LLM** or a custom LLM connector is selected, AI-powered features will default to that connector regardless of which connector was used most recently in your environment.
- **Disallow all other connectors**: When this setting is disabled, whenever you use an AI-powered feature you can select which connector should power it. Enable it to prevent connectors other than the default connector from being used in your space. Default setting: disabled.
- **AI feature visibility**: This button opens the current Space's settings page, where you can specify which features are enabled in your environment, including AI-powered features.
- **Chat experience**: {applies_to}`stack: preview 9.3` Select whether to use AI Assistant or AI Agent. For information about choosing one, refer to [Compare AI Agent and AI Assistant](/explore-analyze/ai-features/ai-chat-experiences/ai-agent-or-ai-assistant.md).
- **AI Assistant visibility**: This setting allows you to choose which AI Assistants are available to use and where. There are several options:
- **Only in their solutions** (default): The Security AI Assistant appears in {{elastic-sec}}, and the {{obs-ai-assistant}} appears in {{es}} and {{observability}}.
- **{{obs-ai-assistant}} in other apps**: The {{obs-ai-assistant}} appears throughout {{kib}} regardless of solution. The Security AI Assistant does not appear anywhere.
Expand All @@ -55,6 +56,7 @@ The **GenAI Settings** page has the following settings:
The **GenAI Settings** page has the following settings:

- **Default AI Connector**: Click **Manage connectors** to open the **Connectors** page, where you can create or delete AI connectors. To update these settings, you need the `Actions and connectors: all` [{{kib}} privilege](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md).
- **Chat experience**: {applies_to}`serverless: preview` Select whether to use AI Assistant or AI Agent. For information about choosing one, refer to [Compare AI Agent and AI Assistant](/explore-analyze/ai-features/ai-chat-experiences/ai-agent-or-ai-assistant.md).
- **AI feature visibility**: Click **Go to Permissions tab** to access the active {{kib}} space's settings page, where you can specify which features each [user role](/deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md) has access to in your environment. This includes AI-powered features.

:::
Expand Down
2 changes: 1 addition & 1 deletion explore-analyze/toc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ toc:
- file: ai-features/llm-guides/connect-to-lmstudio-observability.md
- file: ai-features/llm-guides/connect-to-lmstudio-security.md
- file: ai-features/llm-guides/connect-to-vLLM.md
- hidden: ai-features/ai-agent-or-ai-assistant.md
- file: ai-features/ai-chat-experiences/ai-agent-or-ai-assistant.md
- file: discover.md
children:
- file: discover/discover-get-started.md
Expand Down
3 changes: 3 additions & 0 deletions redirects.yml
Original file line number Diff line number Diff line change
Expand Up @@ -631,3 +631,6 @@ redirects:
# Move CCS feature docs to explore-analyze
'solutions/search/cross-cluster-search.md': 'explore-analyze/cross-cluster-search.md'
'solutions/search/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md': 'explore-analyze/cross-cluster-search/using-resolve-cluster-endpoint-before-cross-cluster-search.md'

# Related to https://github.com/elastic/docs-content/pull/4438
'explore-analyze/ai-features/ai-agent-or-ai-assistant.md': 'explore-analyze/ai-features/ai-chat-experiences/ai-agent-or-ai-assistant.md'
Loading