Add "Switch to Agent Builder" doc for AI assistants #4438
Conversation
Vale Linting ResultsSummary: 1 suggestion found 💡 Suggestions (1)
|
🔍 Preview links for changed docs |
leemthompo
left a comment
leemthompo
left a comment
There was a problem hiding this comment.
Thanks for getting the ball rolling on this! I know the PR is very preliminary but since we last chatted a lot of previously open questions are now basically answered, so hopefully these little notes will help clarify a few things :-)
|
|
||
| # Switch to AI Agent | ||
|
|
||
| AI Agent is a technical preview chat experience designed to replace Elastic Assistant for {{observability}} & Search and Elastic Assistant for Security. |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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 is a technical preview chat experience designed to replace Elastic Assistant for {{observability}} & Search and Elastic Assistant for Security. | ||
|
|
||
| AI Agent is built on Elastic's [Agent Builder](/solutions/search/elastic-agent-builder.md) platform. It enables a more cohesive AI chat experience across all Elastic's products, and lets you design your own purpose-built agents. You can create agents for use in different workflows, and give them precise access to the tools and data they need. |
There was a problem hiding this comment.
I'm not even sure if we're calling this "AI Agent"? I'm not sure if all product team are aligned on the naming, but we can check this after Xmas. I'm sure there will be some re-naming in the next or future releases, one way or another, so let's just keep tabs on that.
FWIW "names in sidenav" map poorly to the actual feature 'Agent Builder' 😄
For example, Agent Builder is currently under "Agents" in the ES sidenav
There was a problem hiding this comment.
We should be aligning on the platform-level "Agent Builder" as the new thing
AI assistant functionality will be replaced by new stuff provided by AB, including new built-in agents and new built-in tools
There was a problem hiding this comment.
I learned last week that all new built-in tools will be available in any solution's Agent Builder instance, so all built-in tools are basically "platform tools"
We need to confirm if the same is true for new built-in "sub" agents
| - **Audit logging** | ||
| - **Quick prompts** | ||
|
|
||
| In addition, AI Agent chats won't show a preview of data you attach to a message, such as Alerts and Attacks. |
There was a problem hiding this comment.
AI Agent Agent Builder chats
There was a problem hiding this comment.
that describes the new AI Agent chat experience
just TBC, we should be documenting the AB chat experience in one spot: https://www.elastic.co/docs/solutions/search/agent-builder/chat
There was a problem hiding this comment.
What you [and Mike] need to figure out is what the diff is in the flyout experience versus the standalone chat experience. We can then determine if we can continue documenting everything under the AB umbrella, or if it makes sense to break out the flyout stuff into the Security + Obs solution docs, respectively.
As I mentioned last week, discussing this with the AB product and design team, there is one chat experience, the AB chat, and it will be available in a full-page standalone view (what's currently available in 9.2 in ES solution) and a flyout in 9.3. But it's the same chat functionality. So, turns out we shouldn't need to break out the flyout stuff into the Security + Obs solution docs.
|
|
||
| Some of the functionality supported by Elastic's AI Assistants is not supported by AI Agents. The differences vary by solution. | ||
|
|
||
| ### Feature differences in {{elastic-sec}} |
There was a problem hiding this comment.
ultimately, I think this should be a table comparing functionality across obs (+ search) assistant, sec assistant, and AB
leemthompo
changed the title
leemthompo
changed the title
Addresses #4204, and partly addresses #522 by creating a new page in the explore-analyze AI section that describes the new AI Agent chat experience, and informs users about the option to opt in to it in 9.3.
Hopefully this can be a starting point for the team to build on. I'm sure I didn't get everything right, and I didn't try to tackle the Observability or Search details, but I have a pretty good picture of the opt-in flow for Observability and Security, and the feature differences in the flyout chat experience for Security, so I wanted to get that on paper.
I put the new page in the AI section we've been working on, in a new folder called ai-chat-experiences. But I didn't create a landing page for that section or move ai-assistant.md into the new folder, because I didn't want to overcommit yet since the question of creating a new section wasn't settled last time we talked about it. I am in favor of a new section because the two chat experiences will probably be coexisting for a while, I'd guess at least 6 months, but I'm open to other ways of handling it. If we agree on a new section, I'll move the ai-assistant.md page in, make a landing page, and add a redirect.
I also have this statement from @leemthompo bouncing around my head, reviewers take note:
I also decided not to document the pop-up opt-in flow, but rather to just send people to the GenAI settings page if they want to opt in, since the opt-in popup experience won't always be available.
Generative AI disclosure