refactor(search): updates copy for getting started elasti ai agent#265597

Merged

TattdCodeMonkey merged 1 commit into

elastic:mainfrom

TattdCodeMonkey:refactor-gs-agent-onboarding-cta-copy

Apr 24, 2026

Contributor

TattdCodeMonkey commented Apr 24, 2026 •

edited by kibanamachine

Loading

Summary

Update copy for Getting start elastic ai agent panel.

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.


          refactor(search): updates copy for getting started elasti ai agent

4a6673c

TattdCodeMonkey added the release_note:skip label

TattdCodeMonkey requested a review from a team as a code owner

April 24, 2026 17:53

TattdCodeMonkey added Team:Search backport:version v9.4.0 v9.5.0 labels

Contributor

macroscopeapp Bot commented Apr 24, 2026

Approvability

Verdict: Would Approve

This PR updates two UI text strings to rename 'Elasticsearch Agent' to 'Elastic AI Agent'. The changes are pure copy updates with no impact on runtime behavior.

^{Macroscope would have approved this PR. A repo admin can enable approvability here.}

Contributor

elasticmachine commented Apr 24, 2026

💚 Build Succeeded

Buildkite Build
Commit: 4a6673c

Metrics [docs]

✅ unchanged

wildemat approved these changes

View reviewed changes

TattdCodeMonkey merged commit 2cc90df into elastic:main

34 checks passed

Contributor

kibanamachine commented Apr 24, 2026

Starting backport for target branches: 9.4

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

Contributor

kibanamachine commented Apr 24, 2026

💔 All backports failed

Status	Branch	Result
❌	9.4	Backport failed because of merge conflicts You might need to backport the following PRs to 9.4: - [Search] Getting Started UX clean-up (#262634)

Manual backport

To create the backport manually run:

node scripts/backport --pr 265597

Questions ?

Please refer to the Backport tool documentation

rbrtj pushed a commit to walterra/kibana that referenced this pull request


          refactor(search): updates copy for getting started elasti ai agent (e…

0ddbb44

…lastic#265597)

## Summary

Update copy for Getting start elastic ai agent panel.

### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
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](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] 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](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

SoniaSanzV pushed a commit to SoniaSanzV/kibana that referenced this pull request


          refactor(search): updates copy for getting started elasti ai agent (e…

062c60f

…lastic#265597)

## Summary

Update copy for Getting start elastic ai agent panel.

### Checklist

Check the PR satisfies following conditions. 

Reviewers should verify this PR satisfies this list as well.

- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
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](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [ ] 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](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

kibanamachine mentioned this pull request

[Search]Add custom telemetry events #265310

Merged

8 tasks

kibanamachine added the backport missing label

Contributor

kibanamachine commented Apr 28, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 265597 locally
cc: @TattdCodeMonkey

9 similar comments

Contributor

kibanamachine commented Apr 29, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 265597 locally
cc: @TattdCodeMonkey

Contributor

kibanamachine commented Apr 30, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 265597 locally
cc: @TattdCodeMonkey

Contributor

kibanamachine commented May 1, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 265597 locally
cc: @TattdCodeMonkey

Contributor

kibanamachine commented May 4, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 265597 locally
cc: @TattdCodeMonkey

Contributor

kibanamachine commented May 5, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 265597 locally
cc: @TattdCodeMonkey

Contributor

kibanamachine commented May 6, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 265597 locally
cc: @TattdCodeMonkey

Contributor

kibanamachine commented May 8, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 265597 locally
cc: @TattdCodeMonkey

Contributor

kibanamachine commented May 11, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 265597 locally
cc: @TattdCodeMonkey

Contributor

kibanamachine commented May 12, 2026

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 265597 locally
cc: @TattdCodeMonkey

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport missing backport:version release_note:skip Team:Search v9.4.0 v9.5.0