[unification][oblt] Integrate AI Assistant CTA#215207
[unification][oblt] Integrate AI Assistant CTA#215207clintandrewhall wants to merge 4 commits intoelastic:mainfrom
Conversation
|
Pinging @elastic/obs-ai-assistant (Team:Obs AI Assistant) |
d5771d1 to
d9147a7
Compare
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
78b05ba to
f191911
Compare
...kages/shared/ai-assistant/ai-assistant-cta/install_knowledge_base/install_knowledge_base.tsx
Show resolved
Hide resolved
stephmilovic
left a comment
There was a problem hiding this comment.
LGTM for the Security GenAI changes. Code review only, thanks!
...kages/shared/ai-assistant/ai-assistant-cta/install_knowledge_base/install_knowledge_base.tsx
Outdated
Show resolved
Hide resolved
x-pack/platform/packages/shared/kbn-ai-assistant/src/chat/welcome_message.tsx
Show resolved
Hide resolved
|
When opening the AI Assistant, before the “Install” button appears, there is a brief flash of another element. It is unclear what this element is, but it appears momentarily before the correct UI is displayed. Screen.Recording.2025-03-26.at.23.53.20.mov |
| </EuiFlexGroup> | ||
| </EuiPanel> | ||
| </EuiFlexItem> | ||
| {connectors?.length ? ( |
There was a problem hiding this comment.
Why don’t we allow navigating to a new conversation when there are no connectors?
Currently, if there is no connector, we show a button to add one directly from the AI Assistant, without requiring navigation to the connector settings page. However, if a user previously had a connector, started a conversation, and then deleted the connector, they can still see the list of past conversations.
In this scenario, we should allow the user to navigate back to the “New Conversation” page from the “Add Connector” button.
There was a problem hiding this comment.
This should be raised with @isaclfreire and others involved in the unified design. The designs make no allowances for "New Conversation" to be available.
|
@arturoliduena The "create connector" portion of the flow is flashing because retrieving the current connector and knowledge base state is delegated to a hook, which executes after the first render. I didn't have the depth of knowledge of the codebase to account for that until you pointed it out, but can look into it. I welcome commits in the meantime! |
8bf03eb to
5f30775
Compare
e680d6c to
5f1e378
Compare
|
@viduni94 @arturoliduena I was able to address all of your feedback with my latest commit: Loading stateConversation widthKnowledge base "flashing" |
5f1e378 to
770b0c0
Compare
|
Pinging @elastic/fleet (Team:Fleet) |
|
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
|
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
rmyz
left a comment
There was a problem hiding this comment.
Infra & Services changes LGTM
d8fc17f to
502d74c
Compare
x-pack/platform/packages/shared/kbn-ai-assistant/src/chat/incorrect_license_panel.tsx
Show resolved
Hide resolved
| ); | ||
|
|
||
| const isConnectorReady = useMemo( | ||
| () => !connectors.error && connectors.connectors?.length && connectors.connectors.length > 0, |
There was a problem hiding this comment.
Why do we have both connectors.connectors?.length and connectors.connectors.length > 0 here?
Isn't checking for connectors.connectors?.length automatically mean connectors.connectors.length > 0 as well?
There was a problem hiding this comment.
It just eliminates the undefined check for clarity. Happy to change it, just submit a suggestion and I'll merge it... or I can just change it.
💔 Build Failed
Failed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
Page load bundle
History
|



Summary
This PR aligns the AI Assistant with the unified design for an Assistant.
No Connector
Before
After
No Knowledge Base
Before
After
Installing Knowledge Base
Before
After
Ready to Help
Before
After