feat(standard): Hide Code Interpreter toggle in Standard agent loop behind FF

[Elaina-Lee]

Commit Type

• feature - New functionality
• fix - Bug fix
• refactor - Code restructuring without behavior change
• perf - Performance improvement
• docs - Documentation update
• test - Test-related changes
• chore - Maintenance/tooling

Risk Level

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

What & Why

Adds Code Interpreter support for Standard agent loops, gated behind a feature flag (enable-code-interpreter-standard). This mirrors the existing Consumption Code Interpreter toggle (#8854) but targets Standard workflows.

When the feature flag is disabled, the builtinTools property is stripped from the agent manifest so the Code Interpreter option is hidden from users.

Impact of Change

• Users: No change until the feature flag is enabled. When enabled, Standard agent loop UIs will surface a Code Interpreter toggle.
• Developers: Adds enableCodeInterpreterStandard function in experimentationFlags.ts and useShouldEnableCodeInterpreterStandard hook in designer-v2/core/utils/experimentation.ts; modifies StandardOperationManifestService.getOperationManifest() to strip builtinTools from the agent manifest when the feature flag is off.
• System: Small change — an async feature flag check added to manifest generation for Standard agent operations; minimal perf impact but may affect startup/manifest fetch timing slightly.

Test Plan

• Unit tests added/updated
• E2E tests added/updated
• Manual testing completed
• Tested in:

Unit tests added

• experimentationFlags.spec.ts — Mocks ExperimentationService().isFeatureEnabled to return true/false and asserts enableCodeInterpreterStandard() (and the other flag helpers) resolve accordingly.
• standardOperationManifest.spec.ts — Tests StandardOperationManifestService.getOperationManifest for the agent operation:
  • When the flag is disabled: asserts builtinTools is absent from the returned manifest.
  • When the flag is enabled: asserts the manifest is returned unchanged with builtinTools present.
  • Verifies the original manifest in supportedBaseManifestObjects is not mutated when stripping builtinTools.

Contributors

Screenshots/Videos

[github-actions]

🤖 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(standard): Hide Code Interpreter toggle in Standard agent loop behind FF
• Issue: Title is clear but uses the abbreviation "FF" (feature flag) which may be unclear to some readers. It could be slightly more descriptive about which feature flag is used to make it easier to scan in release notes and changelogs.
• Recommendation: Make the flag explicit and avoid abbreviations. Example: feat(standard): Gate Code Interpreter toggle in Standard agent loop behind feature flag enable-code-interpreter-standard

---

✅ Commit Type

• Properly selected (feature).
• Note: Only one commit type is selected which is correct for this change.

---

✅ Risk Level

• The PR marks Low risk and the repository label risk:low is present. Based on the diff (feature-flagged change, small modifications to manifest generation, and unit tests added), I agree with the Low risk assessment.

---

✅ What & Why

• Current: Adds Code Interpreter support for Standard agent loops gated behind a feature flag (enable-code-interpreter-standard). When the flag is off, builtinTools is stripped from the agent manifest so the UI toggle is hidden.
• Issue: None — the section is clear and concise.
• Recommendation: (Optional) You may include the explicit function names added (enableCodeInterpreterStandard, useShouldEnableCodeInterpreterStandard) inline to make it slightly easier for reviewers scanning the PR.

---

✅ Impact of Change

• Impact section is well-structured and accurate.
• Recommendation: Small wording suggestions to make the impacts explicit:
  • Users: No change until the feature flag is enabled; when enabled, the Standard agent loop UI surfaces a Code Interpreter toggle.
  • Developers: Adds enableCodeInterpreterStandard to experimentation flags, a useShouldEnableCodeInterpreterStandard hook in designer-v2, and modifies StandardOperationManifestService.getOperationManifest() to conditionally strip builtinTools.
  • System: Adds an async feature-flag check during manifest generation for agent ops; performance impact expected to be negligible.

---

✅ Test Plan

• Unit tests were actually added (two new spec files) and the Test Plan in the body correctly describes them.
• Assessment: The Unit tests cover enable/disable behaviors and confirm the original manifest isn't mutated. Good.
• E2E tests: none added — acceptable for this scope because behavior is feature-flagged and validated via unit tests and manual testing. Make sure the manual testing steps are recorded somewhere (PR comment or test plan doc) for future audits.

---

⚠️ Contributors

• Current: (Missing list of contributors)
• Assessment: Optional but recommended. If others (PMs, designers, reviewers) contributed, add their GitHub handles in this section so credit is tracked.

---

⚠️ Screenshots/Videos

• Current: None provided.
• Assessment: This PR hides/shows a UI toggle — a small visual change. It's recommended to include a before/after screenshot to make visual verification easier for reviewers. If you intentionally omitted visuals because the change is purely behind a flag and not enabled in the default environment, note that in the PR body (e.g., "UI screenshots omitted because the feature flag is off by default").

---

Summary Table

Section	Status	Recommendation
Title	⚠️	Expand "FF" to the full phrase and optionally reference the exact flag name.
Commit Type	✅	No change needed.
Risk Level	✅	No change needed (Low is appropriate).
What & Why	✅	Consider listing new function/hook names inline for quick scan.
Impact of Change	✅	No change needed.
Test Plan	✅	Ensure manual testing steps are recorded somewhere.
Contributors	⚠️	Add contributor handles if applicable.
Screenshots/Videos	⚠️	Add before/after screenshot or note why omitted.

---

Final Message
Please update the PR title to avoid the abbreviation and consider making the feature flag explicit (suggested title above). Add contributors if others helped, and include screenshots or a short note explaining why screenshots are omitted. The body, test coverage, and the included risk label are all consistent and sufficient — I agree this is a Low risk, feature-flagged change and the PR can pass once the small PR metadata improvements are addressed. Thank you!

---

Last updated: Fri, 06 Mar 2026 23:14:12 GMT

[Copilot]

Pull request overview

This PR adds Code Interpreter toggle support to the Standard agent loop, gated behind a new experimentation feature flag (enable-code-interpreter-standard). It mirrors the identical Consumption implementation introduced in PR #8854. When the flag is disabled, the builtinTools property is stripped from the Standard agentloop manifest at runtime so the Code Interpreter option stays hidden from users.

Changes:

• New ENABLE_CODE_INTERPRETER_STANDARD flag constant and enableCodeInterpreterStandard() async function in experimentationFlags.ts
• New useShouldEnableCodeInterpreterStandard() React hook in designer-v2/experimentation.ts
• StandardOperationManifestService.getOperationManifest now checks the flag for agentType and removes builtinTools from the cloned manifest when the flag is off

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
libs/logic-apps-shared/src/designer-client-services/lib/experimentationFlags.ts	Adds the ENABLE_CODE_INTERPRETER_STANDARD flag string constant and enableCodeInterpreterStandard() function
libs/designer-v2/src/lib/core/utils/experimentation.ts	Adds useShouldEnableCodeInterpreterStandard() React hook for component-level feature flag consumption
libs/logic-apps-shared/src/designer-client-services/lib/standard/operationmanifest.ts	Wires the flag check into getOperationManifest: strips builtinTools from the agent loop manifest when the flag is disabled

[github-actions]

📊 Coverage Check

The following changed files need attention:

⚠️ libs/designer-v2/src/lib/core/utils/experimentation.ts - 33% covered (needs improvement)
⚠️ libs/logic-apps-shared/src/designer-client-services/lib/standard/operationmanifest.ts - 23% covered (needs improvement)

Please add tests for the uncovered files before merging.