FE/UX: Plan for including specific meta data for agents and flows

Summary

Display helpful metadata for agents and flows in the AI Catalog. This issue serves as a discussion and decision-making point to determine which metadata fields are most valuable to users and technically feasible to implement.

Decisions Made

Attribution: Source Project (Not Author)

Decision: Display the source project instead of individual author attribution.

Rationale:

  • Individual attribution is ambiguous in multi-contributor workflows
  • The project adequately represents those with appropriate permissions to modify/delete the agent/flow
  • Project data is already available via GraphQL (though nullable)
  • Aligns with UX designs showing project ownership on catalog cards

Implementation: Separate issue created: #580280 (closed)

External Agent Identification

Decision: Differentiate External agents via label plus icon, and possibly an avatar.

Current Status:

  • External agents identified by itemType ("third_party_flow" vs "flow")
  • All External agents use same mechanism regardless of provider
  • Cannot reliably determine provider without error-prone URL parsing
  • Legal approval pending for Anthropic icon; Codex icon approved
  • See Brand/Legal issue

Metadata Fields for Future Consideration

  1. Agent Type: Chat-enabled vs background agent as of 2025-11-11, all agents are chat-enabled
  2. Runtime Information: LLM/Model/Version (currently uses user-selected model via GitLab Duo model selection)

Acceptance Criteria

Edited by Angus Ryer