Move Agent Builder docs to E&A #4538
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
charlotte-hoblik
added
the
documentation
Contributor
Vale Linting ResultsSummary: 3 warnings, 48 suggestions found
|
| File | Line | Rule | Message |
|---|---|---|---|
| explore-analyze/ai-features/agent-builder/mcp-server.md | 35 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'versus' instead of 'VS'. |
| explore-analyze/ai-features/agent-builder/permissions.md | 64 | Elastic.EndPuntuaction | Don't end headings with punctuation. |
| explore-analyze/ai-features/agent-builder/tools.md | 13 | Elastic.EndPuntuaction | Don't end headings with punctuation. |
💡 Suggestions (48)
| File | Line | Rule | Message |
|---|---|---|---|
| explore-analyze/ai-features/agent-builder/a2a-server.md | 11 | Elastic.Capitalization | 'Agent-to-Agent (A2A) server' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/a2a-server.md | 27 | Elastic.Capitalization | 'A2A protocol endpoint' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/agent-builder-agents.md | 45 | Elastic.WordChoice | Consider using 'copy' instead of 'clone', unless the term is in the UI. |
| explore-analyze/ai-features/agent-builder/agent-builder-agents.md | 47 | Elastic.WordChoice | Consider using 'copy' instead of 'Clone', unless the term is in the UI. |
| explore-analyze/ai-features/agent-builder/chat.md | 11 | Elastic.Capitalization | ': Agent Chat' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/chat.md | 32 | Elastic.Capitalization | 'Agent Chat GUI' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/chat.md | 65 | Elastic.Capitalization | 'Agent Chat API' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/get-started.md | 67 | Elastic.FutureTense | 'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/ai-features/agent-builder/kibana-api.md | 273 | Elastic.WordChoice | Consider using 'run, start' instead of 'execute', unless the term is in the UI. |
| explore-analyze/ai-features/agent-builder/limitations-known-issues.md | 31 | Elastic.Capitalization | 'A2A streaming not supported' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/limitations-known-issues.md | 45 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| explore-analyze/ai-features/agent-builder/limitations-known-issues.md | 66 | Elastic.Capitalization | 'limitations' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/limitations-known-issues.md | 93 | Elastic.Acronyms | 'MCP' has no definition. |
| explore-analyze/ai-features/agent-builder/limitations-known-issues.md | 99 | Elastic.Acronyms | 'MCP' has no definition. |
| explore-analyze/ai-features/agent-builder/mcp-server.md | 2 | Elastic.Acronyms | 'MCP' has no definition. |
| explore-analyze/ai-features/agent-builder/mcp-server.md | 11 | Elastic.Capitalization | 'Model Context Protocol (MCP) server' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/mcp-server.md | 68 | Elastic.WordChoice | Consider using 'run, start' instead of 'execute', unless the term is in the UI. |
| explore-analyze/ai-features/agent-builder/mcp-server.md | 127 | Elastic.FutureTense | 'you'll receive' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/ai-features/agent-builder/models.md | 58 | Elastic.Versions | Use 'or earlier' instead of 'or older' when referring to versions. |
| explore-analyze/ai-features/agent-builder/models.md | 62 | Elastic.Acronyms | 'GPT' has no definition. |
| explore-analyze/ai-features/agent-builder/models.md | 82 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| explore-analyze/ai-features/agent-builder/permissions.md | 27 | Elastic.Capitalization | 'privileges' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/permissions.md | 37 | Elastic.Capitalization | 'cluster privileges' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/permissions.md | 45 | Elastic.Capitalization | 'index privileges' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/permissions.md | 47 | Elastic.WordChoice | Consider using 'run, start' instead of 'execute', unless the term is in the UI. |
| explore-analyze/ai-features/agent-builder/permissions.md | 50 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| explore-analyze/ai-features/agent-builder/permissions.md | 106 | Elastic.Acronyms | 'MCP' has no definition. |
| explore-analyze/ai-features/agent-builder/permissions.md | 117 | Elastic.Acronyms | 'MCP' has no definition. |
| explore-analyze/ai-features/agent-builder/permissions.md | 120 | Elastic.Acronyms | 'MCP' has no definition. |
| explore-analyze/ai-features/agent-builder/programmatic-access.md | 18 | Elastic.FutureTense | 'will probably' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/ai-features/agent-builder/programmatic-access.md | 18 | Elastic.Acronyms | 'MCP' has no definition. |
| explore-analyze/ai-features/agent-builder/programmatic-access.md | 21 | Elastic.Acronyms | 'MCP' has no definition. |
| explore-analyze/ai-features/agent-builder/tools.md | 62 | Elastic.WordChoice | Consider using 'efficient' instead of 'easy', unless the term is in the UI. |
| explore-analyze/ai-features/agent-builder/tools.md | 204 | Elastic.Acronyms | 'MCP' has no definition. |
| explore-analyze/ai-features/agent-builder/tools.md | 211 | Elastic.WordChoice | Consider using 'efficient' instead of 'easy', unless the term is in the UI. |
| explore-analyze/ai-features/agent-builder/tools/esql-tools.md | 13 | Elastic.Capitalization | 'tools' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/tools/esql-tools.md | 29 | Elastic.WordChoice | Consider using 'run, start' instead of 'Execute', unless the term is in the UI. |
| explore-analyze/ai-features/agent-builder/tools/esql-tools.md | 51 | Elastic.FutureTense | 'will automatically' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/ai-features/agent-builder/tools/esql-tools.md | 55 | Elastic.FutureTense | 'will provide' might be in future tense. Write in the present tense to describe the state of the product as it is now. |
| explore-analyze/ai-features/agent-builder/tools/esql-tools.md | 81 | Elastic.Capitalization | 'documentation' should use sentence-style capitalization. |
| explore-analyze/ai-features/agent-builder/tools/index-search-tools.md | 15 | Elastic.WordChoice | Consider using 'run, start' instead of 'execute', unless the term is in the UI. |
| explore-analyze/ai-features/agent-builder/tools/index-search-tools.md | 38 | Elastic.FirstPerson | Avoid first-person pronouns such as 'my'. |
| explore-analyze/ai-features/agent-builder/tools/index-search-tools.md | 48 | Elastic.Acronyms | 'DSL' has no definition. |
| explore-analyze/ai-features/agent-builder/tools/index-search-tools.md | 49 | Elastic.WordChoice | Consider using 'run, start' instead of 'Execute', unless the term is in the UI. |
| explore-analyze/ai-features/elastic-agent-builder.md | 15 | Elastic.Acronyms | 'MCP' has no definition. |
| explore-analyze/ai-features/elastic-agent-builder.md | 35 | Elastic.Capitalization | 'Agent Chat' should use sentence-style capitalization. |
| explore-analyze/ai-features/elastic-agent-builder.md | 43 | Elastic.Wordiness | Consider using 'act' instead of 'take action'. |
| solutions/search/apis-and-tools.md | 79 | Elastic.WordChoice | Consider using 'run, start' instead of 'execute', unless the term is in the UI. |
Contributor
leemthompo
reviewed
Jan 7, 2026
vishaangelova
approved these changes
Jan 7, 2026
leemthompo
approved these changes
Jan 7, 2026
Contributor
leemthompo
left a comment
leemthompo
left a comment
There was a problem hiding this comment.
Thanks! Let's be sure to confirm redirects are working as expected ASAP once these changes go live 🚀
1 task
leemthompo
added a commit
that referenced
this pull request
Jan 22, 2026
) Agent-builder docs were relocated from `/solutions/search/agent-builder/` to `/explore-analyze/ai-features/agent-builder/` in #4538, but CODEOWNERS was not updated. ## Changes - Added `/explore-analyze/ai-features/agent-builder/ @elastic/developer-docs` to maintain ownership continuity after the move <!-- START COPILOT ORIGINAL PROMPT --> <details> <summary>Original prompt</summary> > > ---- > > *This section details on the original issue you should resolve* > > <issue_title>Update CODEOWNERS for agent-builder docs</issue_title> > <issue_description>## Background > The agent builder docs were moved in #4538 > > ## Tasks: > > - [ ] https://github.com/elastic/docs-content/blob/main/.github/CODEOWNERS needs to be updated accordingly > </issue_description> > > ## Comments on the Issue (you are @copilot in this section) > > <comments> > </comments> > </details> <!-- START COPILOT CODING AGENT SUFFIX --> - Fixes #4573 <!-- START COPILOT CODING AGENT TIPS --> --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey). --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: leemthompo <32779855+leemthompo@users.noreply.github.com> Co-authored-by: Liam Thompson <leemthompo@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR moved the Agent Builder docs to the Explore and analyze section.
Based on this issue: https://github.com/elastic/docs-content-internal/issues/612