Skip to content

[Agent Builder] Recommended Connectors#263865

Merged
zacharyparikh merged 12 commits intoelastic:mainfrom
zacharyparikh:ab/recommended-connectors
Apr 21, 2026
Merged

[Agent Builder] Recommended Connectors#263865
zacharyparikh merged 12 commits intoelastic:mainfrom
zacharyparikh:ab/recommended-connectors

Conversation

@zacharyparikh
Copy link
Copy Markdown
Contributor

@zacharyparikh zacharyparikh commented Apr 16, 2026

Summary

Removes the frontend logic that refers to a static list of connector ids to determine if a connector should be displayed as recommended. Instead now refers to the isRecommended prop that is added in #263843

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests were updated or added to match the most common scenarios
  • If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
  • Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

@zacharyparikh zacharyparikh self-assigned this Apr 16, 2026
@zacharyparikh zacharyparikh added release_note:skip Skip the PR/issue when compiling release notes backport:version Backport to applied version labels v9.4.0 v9.5.0 labels Apr 16, 2026
async () => {
const query = useQuery({
queryKey: [...QUERY_KEY, featureId],
queryFn: async () => {
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Just changing to object signature which will be required in v5

const NO_DEFAULT_CONNECTOR = 'NO_DEFAULT_CONNECTOR';

const selectDefaultConnector = ({ connectors }: { connectors: InferenceConnector[] }) => {
const recommendedId = getFirstRecommendedConnectorId(connectors.map((c) => c.connectorId));
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This path gets the InferenceConnector objects directly from InferenceServerStart.getConnectorList(). Am I correct in assuming these will not have the isRecommended prop? If that is the case then is it correct to just remove this logic that checks for a recommended connector or should we be doing something else here?
cc @pgayvallet

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yeah that's right. We need to change our server-side logic to do the same as the browser-side, but the searchInferenceEndpoints plugin do not expose that API server-side at the moment, so let's consider that out of scope of the current PR. I'll adapt independently.

@zacharyparikh zacharyparikh marked this pull request as ready for review April 16, 2026 17:36
@zacharyparikh zacharyparikh requested review from a team as code owners April 16, 2026 17:36
@zacharyparikh zacharyparikh added the feature:agent-builder Identify agent builder functionalities to be grouped together for release notes label Apr 16, 2026
const NO_DEFAULT_CONNECTOR = 'NO_DEFAULT_CONNECTOR';

const selectDefaultConnector = ({ connectors }: { connectors: InferenceConnector[] }) => {
const recommendedId = getFirstRecommendedConnectorId(connectors.map((c) => c.connectorId));
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yeah that's right. We need to change our server-side logic to do the same as the browser-side, but the searchInferenceEndpoints plugin do not expose that API server-side at the moment, so let's consider that out of scope of the current PR. I'll adapt independently.

@zacharyparikh
Copy link
Copy Markdown
Contributor Author

@elasticmachine merge upstream

@elasticmachine
Copy link
Copy Markdown
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
agentBuilder 1362 1361 -1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
agentBuilder 1.1MB 1.1MB -163.0B
automaticImport 330.2KB 330.2KB +15.0B
observabilityAgentBuilder 23.8KB 23.8KB +15.0B
securitySolution 11.7MB 11.7MB +15.0B
streamsApp 2.0MB 2.0MB +15.0B
workplaceAIApp 513.8KB 513.8KB +15.0B
total -88.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
elasticAssistant 265.0KB 265.0KB +15.0B
observabilityAIAssistant 59.7KB 59.7KB +15.0B
total +30.0B

History

cc @zacharyparikh

@zacharyparikh zacharyparikh merged commit c718d02 into elastic:main Apr 21, 2026
18 checks passed
@kibanamachine
Copy link
Copy Markdown
Contributor

Starting backport for target branches: 9.4

https://github.com/elastic/kibana/actions/runs/24747235002

@kibanamachine
Copy link
Copy Markdown
Contributor

💚 All backports created successfully

Status Branch Result
9.4

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Apr 21, 2026
# Backport

This will backport the following commits from `main` to `9.4`:
- [[Agent Builder] Recommended Connectors
(#263865)](#263865)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Zachary
Parikh","email":"zachary.parikh@elastic.co"},"sourceCommit":{"committedDate":"2026-04-21T21:25:18Z","message":"[Agent
Builder] Recommended Connectors
(#263865)","sha":"c718d0253ebe60230eb87ffd8711e46344ccd682","branchLabelMapping":{"^v9.5.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","v9.4.0","feature:agent-builder","v9.5.0"],"title":"[Agent
Builder] Recommended
Connectors","number":263865,"url":"https://github.com/elastic/kibana/pull/263865","mergeCommit":{"message":"[Agent
Builder] Recommended Connectors
(#263865)","sha":"c718d0253ebe60230eb87ffd8711e46344ccd682"}},"sourceBranch":"main","suggestedTargetBranches":["9.4"],"targetPullRequestStates":[{"branch":"9.4","label":"v9.4.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.5.0","branchLabelMappingKey":"^v9.5.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/263865","number":263865,"mergeCommit":{"message":"[Agent
Builder] Recommended Connectors
(#263865)","sha":"c718d0253ebe60230eb87ffd8711e46344ccd682"}}]}]
BACKPORT-->

Co-authored-by: Zachary Parikh <zachary.parikh@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:version Backport to applied version labels feature:agent-builder Identify agent builder functionalities to be grouped together for release notes release_note:skip Skip the PR/issue when compiling release notes v9.4.0 v9.5.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants