Skip to content

feat(Designer): Info bubble for code interpreter (#9043)#9047

Merged
Elaina-Lee merged 3 commits intohotfix/v5.294from
cherry-pick/9043
Apr 10, 2026
Merged

feat(Designer): Info bubble for code interpreter (#9043)#9047
Elaina-Lee merged 3 commits intohotfix/v5.294from
cherry-pick/9043

Conversation

@Elaina-Lee
Copy link
Copy Markdown
Contributor

Commit Type

  • feature - New functionality

Risk Level

  • Low - Minor changes, limited scope
  • Medium - Moderate changes, some user impact
  • High - Major changes, significant user/system impact

What & Why

Cherry-picks PR #9043 from main into the hotfix/v5.294 release branch.

Adds an info tooltip next to the Code Interpreter display name in the built-in tools editor for consumption agent loop workflows. The tooltip informs users that an integration account is required to enable code interpreter, with a "Read more" link to the relevant Microsoft Learn documentation.

This is consumption-only — the infoMessage, infoLinkText, and infoLinkUrl fields are added to the consumption agent loop manifest's code_interpreter option, and the BuiltinToolOption interface supports them optionally.

Impact of Change

  • Users: Consumption workflow users see an info icon next to Code Interpreter with guidance about the integration account requirement
  • Developers: BuiltinToolOption interface gains three optional fields (infoMessage, infoLinkText, infoLinkUrl) for adding info tooltips to any built-in tool option
  • System: No performance or architecture impact; additive change only

Test Plan

Contributors

@Elaina-Lee

…gent loop (#9043)

* feat(DesignerUI): Add info bubble for code interpreter in consumption agent loop

Add an info tooltip next to the Code Interpreter display name in the built-in tools editor,
informing users that an integration account is required. The tooltip includes a "Read more"
link to the relevant Microsoft Learn documentation. This is consumption-only, driven by
the manifest's editorOptions.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* fix(DesignerUI): Update code interpreter description wording

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

* fix(DesignerUI): Update builtintools snapshot for toolNameRow wrapper

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 10, 2026

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

⚠️ PR Title

  • Current: feat(Designer): Info bubble for code interpreter (#9043)
  • Issue: The title is mostly clear but contains the original PR number (feat(Designer): Add info bubble for code interpreter in consumption agent loop #9043). When cherry-picking into a hotfix branch it's helpful to either remove the original PR number from the title (to avoid noise) or explicitly note the cherry-pick/hotfix context. Otherwise this is a fine descriptive title.
  • Recommendation: Prefer one of:
    • feat(designer): Add info tooltip for Code Interpreter
    • cherry-pick: Add info tooltip for Code Interpreter (hotfix/v5.294)

Commit Type

  • Properly selected (feature)
  • Only one type selected which is correct for this change

Risk Level

  • The PR is labelled risk:low and the changes are small UI additions, an additive interface change, and a manifest update for consumption only. Unit snapshot/test updates are present. I agree risk:low is appropriate.

What & Why

  • Current: "Cherry-picks PR feat(Designer): Add info bubble for code interpreter in consumption agent loop #9043 from main into the hotfix/v5.294 release branch... Adds an info tooltip next to the Code Interpreter display name..."
  • Issue: None significant — the description explains the change and why it was cherry-picked into the hotfix branch.
  • Recommendation: (Optional) You could mention the target hotfix branch in the PR title (see Title recommendation), but the body already documents it.

Impact of Change

  • The Impact of Change section is clear and accurate.
  • Recommendation: Keep as-is. Example breakdown is good:
    • Users: Consumption workflow users see an info icon next to Code Interpreter with guidance about integration account requirement
    • Developers: Interface gains three optional fields on BuiltinToolOption
    • System: Additive UI/manifest changes only

Test Plan

  • Test plan claims unit tests updated and manual testing completed. I verified the code diff includes an updated spec and snapshot (builtintools.spec.tsx and its snapshot), so the unit test change is present.
  • E2E tests are not added — acceptable for a small UI/manifest change. If you think an E2E is warranted, please add; otherwise include a brief note why it's unnecessary (the PR already references verification in the original PR).

Contributors

  • Contributors are listed (@Elaina-Lee). Good — credit is present.

⚠️ Screenshots/Videos

  • No screenshots included. This is acceptable for a small tooltip change, but if you want to make UI review easier you may add a small screenshot or short animated gif showing the tooltip on hover/focus.

Summary Table

Section Status Recommendation
Title ⚠️ Remove the original PR number or add explicit cherry-pick context in the title
Commit Type No change needed
Risk Level No change needed (matches labels and diff)
What & Why No change needed
Impact of Change No change needed
Test Plan Unit test updates present; E2E optional
Contributors No change needed
Screenshots/Videos ⚠️ Optional: add screenshot/gif if you want easier UI review

Final notes:

  • Overall this PR is well-formed and aligns with the repository's PR body template. I verified the code diff: the change adds an optional tooltip/info icon UI in builtintools, updates styles and imports, adds three optional fields to the BuiltinToolOption interface, and updates the consumption manifest to include the info text and link for the code_interpreter option. Unit test snapshot/spec updates are present in the diff confirming tests were updated.

Please update the PR title if you want to remove the original PR number or make the cherry-pick/hotfix intent more explicit. Otherwise this PR passes validation.

Thank you for the clear PR body and tests!


Last updated: Fri, 10 Apr 2026 23:19:16 GMT

@Elaina-Lee Elaina-Lee added the risk:low Low risk change with minimal impact label Apr 10, 2026
@Elaina-Lee Elaina-Lee changed the title feat(Designer): Cherry-pick info bubble for code interpreter (#9043) feat(Designer): Info bubble for code interpreter (#9043) Apr 10, 2026
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 10, 2026

📊 Coverage Check

No source files changed in this PR.

Elaina-Lee and others added 2 commits April 10, 2026 16:08
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@Elaina-Lee Elaina-Lee merged commit 156a616 into hotfix/v5.294 Apr 10, 2026
11 checks passed
@Elaina-Lee Elaina-Lee deleted the cherry-pick/9043 branch April 10, 2026 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-validated risk:low Low risk change with minimal impact

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants