Hi @vvempati
Could you please review this MR?

Sahil Sharma (7e44f7a4) at 18 Mar 13:29

Sahil Sharma (a3390717) at 18 Mar 13:24

Sahil Sharma (37666073) at 18 Mar 11:59

Sahil Sharma (1debd42a) at 18 Mar 11:54

Sahil Sharma (f6c847b2) at 18 Mar 08:27

... and 473 more commits

What does this MR do and why?

Add Pipeline Builder foundational agent

• Add Pipeline Builder agent definition with catalog ID 1004583
• Add feature flag foundational_pipeline_authoring_agent (disabled by default)
• Add feature flag check in foundational chat agents resolver
• Add documentation for Pipeline Builder agent
• Rename agent from "Pipeline Authoring" to "AI Pipeline Builder" across docs, definitions, resolver, and specs

Changelog: added

Behind a feature flag. Rollout issue - #588564

References

Changes in AI Assist repo - gitlab-org/modelops/applied-ml/code-suggestions/ai-assist!4461

Screenshots or screen recordings

NA

How to set up and validate locally

NA

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #587460

Removing pipeline:run-flaky-tests label because the flakey E2E pipeline has passed now and the qa:rspec-internal was failing because this label was set.

Sahil Sharma (39ddc394) at 17 Mar 20:01

... and 259 more commits

Hi @ekigbo
I've resolved your & Duo's comments. Let me know if this MR looks good to you now 🏓

Updated to use props now.

Yeah, now I've updated the assertion here to now check on UI updates instead of wrapper.vm.stageStatusSubscription

Sahil Sharma (9ea778f7) at 17 Mar 18:23

17th March 2026

Hey @kentvuoung, README looks solid. Good documentation of your GDK setup challenges and how you debugged the CI mock failures.

On your "under review" MR, I would suggest taking a look at Duo's feedback as well and see if that needs to be implemented or not.

Also, as you continue updating the README, try to tighten it up a bit. Some of the same points come through in multiple sections (e.g. the problem description, solution approach, and implementation notes cover similar ground). Keeping it concise and avoiding repetition will make it easier for reviewers to follow your progress at a glance.

Hey @riad.benyamna2020, I'm one of the mentors in the AI Corps program. Wanted to share some context that might help as you work on this.

This issue was originally created in 2017, and the codebase has evolved quite a bit since then. Legacy issues have largely transformed into work items, and Chad Lavimoniere's comment from June 2025 confirms the bug still exists in that newer flow. As you start digging in, make sure you're looking at where this behavior lives today, not just the files referenced in the original issue description.

Also, as you explore further, you may find that the complexity here is bigger than it initially looks. The permission logic touches multiple service layers, and there's a question of backend vs frontend scope. I'd suggest spending some time mapping out the full impact surface before jumping into code.

From there, try to identify an iterable approach: scope a specific, shippable piece of the fix rather than trying to solve the whole thing at once. That way you'll have something concrete to ship by the end of the program, even if the full fix ends up being larger.

Feel free to tag me if you have questions or want to talk through your approach.

17th March 2026

Hey @riad.benyamna2020, good start on Phase 1. Your problem description is clear and the expected vs current behavior section shows you understand what's going wrong.
A couple of things to double-check: take another look at the file paths you've listed under Affected Components. Make sure you're referencing the right class where the logic you described actually lives, since legacy issues have evolved into work items after that issue was created.
For next steps, I'd love to see you start filling in Phase 2. Specifically:

• Have you been able to get GDK set up? If you ran into any issues there, let me know.
• Try to reproduce the bug locally and document the steps
• Start thinking through your solution approach

Tag me once you've made progress on any of these.

17th March 2026

The README still seems to be a blank template and I don't see any issue link as well.
Have you had a chance to pick an issue to work on yet? If you're having trouble finding one or ran into any blockers along the way, feel free to let me know here. Happy to help point you in the right direction.

cc: @Aarzoo-Bansal