## Q1 FY2027 MVP The AI catalog lacks basic mechanisms for community contribution - no attribution, version history, or collaboration tools that incentivize sharing and improving agents. This initiative establishes contributor attribution, collaboration mechanisms, version history, and quality signals to create a foundation for community growth. ##### MVP Scope Contributor attribution, collaboration mechanism for suggestions/issues, version history, quality signals (usage/copy counts), contribution documentation and governance, and ratings/reviews. Excludes advanced collaboration (forking/PRs), monetization, forums, and repo-backed architecture migration. ##### UX outcome Contributors receive visible credit for their work, and users can evaluate community agents through maintainer info, usage signals, and clear contribution paths. The catalog becomes a living ecosystem where agents improve over time rather than static artifacts. <details> <summary>Additional details</summary> ## Description GitLab has an opportunity to build a thriving ecosystem of community-created agents and flows, similar to what exists with CI/CD components. However, the current catalog infrastructure lacks fundamental mechanisms that enable community contribution and collaboration. Contributors cannot receive attribution for agents they create, cannot track changes or improvements over time, and have no way to collaborate with others who want to enhance existing agents. Without these basics, there's no incentive to share agents publicly or improve existing community contributions. This initiative establishes core community infrastructure including contributor attribution, collaboration mechanisms, version history, and quality signals. This creates a foundation for community growth where contributors get recognition for their work and users can trust and improve community-created agents. ## Connection to goal Drives toward 1M LLM requests by expanding the catalog through community contributions. GitLab alone cannot create agents for every use case, but an active community can. More agents in the catalog means more reasons for teams to adopt DAP. Community-maintained agents that improve over time lead to better user experiences and sustained usage. Each community-contributed agent represents net-new LLM request generation that wouldn't exist otherwise. This creates a multiplier effect where community growth directly scales catalog value and DAP adoption. ## Scope **In scope:** - [Contributor attribution](https://gitlab.com/gitlab-org/gitlab/-/issues/582957) ("created by" metadata and display) - [Community contributor badges or recognition](https://gitlab.com/gitlab-org/gitlab/-/issues/587707) - [Quality signals](https://gitlab.com/groups/gitlab-org/-/work_items/20588) - [Display enabled namespace count](https://gitlab.com/gitlab-org/gitlab/-/issues/587713) - Stretch - [Basic collaboration mechanism](https://gitlab.com/groups/gitlab-org/-/work_items/20589) (how to suggest improvements or report issues) **Out of scope:** - Advanced collaboration features (forking, branching, pull requests) - Monetization or paid agent marketplace - Community forums or discussion boards - Repo-backed architecture migration (requires technical spike first) - Integration with external contribution platforms ## UX outcome Contributors who create valuable agents receive visible credit and recognition for their work. When a user discovers a community agent, they can see who maintains it, how many times it's been used or copied, and how to contribute improvements. Users trust community agents because they can evaluate the maintainer and see usage signals. Contributors have a clear path to share their work publicly and iterate on it based on community feedback. The catalog becomes a living ecosystem where agents improve over time rather than static artifacts that decay. ## Success metric - Number of community-contributed agents in public catalog increases from baseline to [- x -] agents by end of Q2 - Community contributor count increases from baseline to [- x -] unique contributors - Agent copy rate (users copying community agents) increases by [- x% -] from baseline </details>