[Agent Builder] Decrease base font sizes in chat UI. - #283254
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
613fe65 to
2f3a15d
Compare
Co-authored-by: Cursor <cursoragent@cursor.com>
dc8449f to
92a22f7
Compare
Co-authored-by: Cursor <cursoragent@cursor.com>
92a22f7 to
d67c4c9
Compare
…copy change. Co-authored-by: Cursor <cursoragent@cursor.com>
1efa77d to
b8a96fd
Compare
Co-authored-by: Cursor <cursoragent@cursor.com>
03056cf to
8a2f21c
Compare
…tatus text. Co-authored-by: Cursor <cursoragent@cursor.com>
3a9bd5e to
42c73ca
Compare
Co-authored-by: Cursor <cursoragent@cursor.com>
| : euiTheme.colors.backgroundBasePlain}; | ||
| min-height: ${isCollapsed ? '0' : INPUT_MIN_HEIGHT}; | ||
| padding: ${euiTheme.size.base} ${euiTheme.size.base} ${euiTheme.size.s} ${euiTheme.size.base}; | ||
| padding: ${euiTheme.size.base}; |
There was a problem hiding this comment.
Evens out the padding in the conversation input.
| closePopover={closePopover} | ||
| panelPaddingSize="xs" | ||
| anchorPosition="downCenter" | ||
| panelPaddingSize="none" |
There was a problem hiding this comment.
This was causing double padding
| import { | ||
| EuiBadge, | ||
| EuiButtonEmpty, | ||
| EuiButton, |
There was a problem hiding this comment.
Results in a bordered button which looks better at full-width than the prior empty button (label floating in center of footer).
|
|
||
| describe('ToolCallGroup', () => { | ||
| it('shows "N tools ran." once every step in the group has a result', () => { | ||
| it('shows "N tools ran" once every step in the group has a result', () => { |
There was a problem hiding this comment.
Opinionated change :)
I felt the periods were unnecessary and, visually, it looks better to remove them.
| </EuiText> | ||
| ); | ||
|
|
||
| const expansionStyles = css` |
There was a problem hiding this comment.
The extra padding make for an awkward alignment. Now flush left like other tool calls.
| responsive={false} | ||
| gutterSize="xs" | ||
| alignItems="center" | ||
| alignItems="baseline" |
There was a problem hiding this comment.
With the smaller font sizes, this makes for better vertical alignment between badge and adjacent text.
|
|
||
| return ( | ||
| <EuiFlexGroup direction="column" gutterSize="s" data-test-subj="agentBuilderThinkingPanel"> | ||
| <EuiFlexGroup direction="column" data-test-subj="agentBuilderThinkingPanel"> |
There was a problem hiding this comment.
Add some vertical spacing in this section now that the font size is smaller; make it less dense.
| <EuiFlexItem grow={false}> | ||
| <EuiIcon | ||
| type={isExpanded ? 'arrowUp' : 'arrowDown'} | ||
| type={isExpanded ? 'chevronSingleDown' : 'chevronSingleRight'} |
There was a problem hiding this comment.
Prefer arrow to point down when open/expanded and right when closed/collapsed.
| onClosePreview={action('close preview')} | ||
| /> | ||
| <EuiSplitPanel.Inner grow={false} paddingSize="none"> | ||
| <EuiSplitPanel.Inner |
There was a problem hiding this comment.
UI bug; mismatched border-radius between container and content.
| text-overflow: ellipsis; | ||
| `; | ||
|
|
||
| const headerBorderRadius = isCanvas |
There was a problem hiding this comment.
UI bug. When showing the attachment UI in the canvas, the header should not have a bottom border radius.
| ol > li > p { | ||
| margin-bottom: ${euiTheme.size.s}; | ||
| } | ||
|
|
There was a problem hiding this comment.
This probably needs to be fixed/changed in EUI, but it helps here in the meantime. Feedback in the Slack channel notes that the bullet lists - within responses - were vertically crowded.
| <EuiButtonEmpty | ||
| iconType="clock" | ||
| size="s" | ||
| size="xs" |
There was a problem hiding this comment.
Made smaller to match size of adjacent buttons
| return ( | ||
| <EuiFlexGroup | ||
| direction="row" | ||
| direction="rowReverse" |
There was a problem hiding this comment.
Move button group to right edge. I felt this improves scanability down the left side of the chat by having one less thing over there. Also, seems like a more natural, common position for such actions (see Cursor).
| import type { EuiThemeComputed } from '@elastic/eui'; | ||
|
|
||
| export const headerHeight = 88; | ||
| export const headerHeight = 64; |
There was a problem hiding this comment.
Decrease to match height of side menu header.
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Page load bundle
Unknown metric groupsshared async chunks total size
total optimizer output size
History
|
## Summary Tighten Agent Builder chat typography and spacing so the conversation UI feels more consistent with the rest of Kibana. ## Changes - Reduce chat message and markdown text from `m` to `s` - Reduce composer/editor font size from `m` to `s` - Shrink conversation header height (`88` → `64`) and more-actions button size (`m` → `s`) - Use smaller control sizes for input popover buttons and round metadata trigger (`xs`) - Tighten round response/input spacing and padding - Align thinking/tool-call step layout, expansion chevrons, and copy (drop trailing periods) - Simplify to-dos header and adjust its padding/type size - fix: Use canvas-specific attachment header radius (`0 4px 0 0`) - fix: Remove sidebar right border; minor connector selector and new-conversation prompt tweaks ##### Screenshots <img width="3172" height="1930" alt="CleanShot 2026-08-06 at 10 58 26@2x" src="https://github.com/user-attachments/assets/62b87ff8-580b-4d12-abba-6bd3326acd45" /> <img width="3172" height="1930" alt="CleanShot 2026-08-06 at 10 57 47@2x" src="https://github.com/user-attachments/assets/b41de9dc-97d4-4a85-91cf-25625588eca4" /> <img width="3172" height="1930" alt="CleanShot 2026-08-06 at 11 00 02@2x" src="https://github.com/user-attachments/assets/943e7575-52af-44fc-b272-3c5aeed7ea73" /> <img width="3172" height="1930" alt="CleanShot 2026-08-06 at 11 16 05@2x" src="https://github.com/user-attachments/assets/051923cb-aa53-42eb-8188-5a5c9e5265df" /> ### 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](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 - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/docs/extend/kibana/contributing/workflow/how-we-use-github#release-notes) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary Tighten Agent Builder chat typography and spacing so the conversation UI feels more consistent with the rest of Kibana. ## Changes - Reduce chat message and markdown text from `m` to `s` - Reduce composer/editor font size from `m` to `s` - Shrink conversation header height (`88` → `64`) and more-actions button size (`m` → `s`) - Use smaller control sizes for input popover buttons and round metadata trigger (`xs`) - Tighten round response/input spacing and padding - Align thinking/tool-call step layout, expansion chevrons, and copy (drop trailing periods) - Simplify to-dos header and adjust its padding/type size - fix: Use canvas-specific attachment header radius (`0 4px 0 0`) - fix: Remove sidebar right border; minor connector selector and new-conversation prompt tweaks ##### Screenshots <img width="3172" height="1930" alt="CleanShot 2026-08-06 at 10 58 26@2x" src="https://github.com/user-attachments/assets/62b87ff8-580b-4d12-abba-6bd3326acd45" /> <img width="3172" height="1930" alt="CleanShot 2026-08-06 at 10 57 47@2x" src="https://github.com/user-attachments/assets/b41de9dc-97d4-4a85-91cf-25625588eca4" /> <img width="3172" height="1930" alt="CleanShot 2026-08-06 at 11 00 02@2x" src="https://github.com/user-attachments/assets/943e7575-52af-44fc-b272-3c5aeed7ea73" /> <img width="3172" height="1930" alt="CleanShot 2026-08-06 at 11 16 05@2x" src="https://github.com/user-attachments/assets/051923cb-aa53-42eb-8188-5a5c9e5265df" /> ### 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](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 - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/docs/extend/kibana/contributing/workflow/how-we-use-github#release-notes) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary Tighten Agent Builder chat typography and spacing so the conversation UI feels more consistent with the rest of Kibana. ## Changes - Reduce chat message and markdown text from `m` to `s` - Reduce composer/editor font size from `m` to `s` - Shrink conversation header height (`88` → `64`) and more-actions button size (`m` → `s`) - Use smaller control sizes for input popover buttons and round metadata trigger (`xs`) - Tighten round response/input spacing and padding - Align thinking/tool-call step layout, expansion chevrons, and copy (drop trailing periods) - Simplify to-dos header and adjust its padding/type size - fix: Use canvas-specific attachment header radius (`0 4px 0 0`) - fix: Remove sidebar right border; minor connector selector and new-conversation prompt tweaks ##### Screenshots <img width="3172" height="1930" alt="CleanShot 2026-08-06 at 10 58 26@2x" src="https://github.com/user-attachments/assets/62b87ff8-580b-4d12-abba-6bd3326acd45" /> <img width="3172" height="1930" alt="CleanShot 2026-08-06 at 10 57 47@2x" src="https://github.com/user-attachments/assets/b41de9dc-97d4-4a85-91cf-25625588eca4" /> <img width="3172" height="1930" alt="CleanShot 2026-08-06 at 11 00 02@2x" src="https://github.com/user-attachments/assets/943e7575-52af-44fc-b272-3c5aeed7ea73" /> <img width="3172" height="1930" alt="CleanShot 2026-08-06 at 11 16 05@2x" src="https://github.com/user-attachments/assets/051923cb-aa53-42eb-8188-5a5c9e5265df" /> ### 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](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 - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/docs/extend/kibana/contributing/workflow/how-we-use-github#release-notes) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) 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. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Summary
Tighten Agent Builder chat typography and spacing so the conversation UI feels more consistent with the rest of Kibana.
Changes
mtosmtos88→64) and more-actions button size (m→s)xs)0 4px 0 0)Screenshots
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*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.