📇 feat: Agent Contact Visibility with Owner Fallback

[peeeteeer]

Implements agent contact visibility for LibreChat issue #12784.

This adds a derived owner_contact fallback to agent API responses when an agent has no explicit support_contact. The fallback is resolved server-side from the first agent owner, preferring ACL ownership and falling back to the legacy author field only when ACL owner data is unavailable. Explicit support contact remains authoritative and is not mixed with owner fallback data.

Changes

• Added shared AgentOwnerContact typing and owner_contact support on agent response types.
• Added shared contact resolution helpers in packages/api.
• Added server-side owner contact attachment through api/server/services/Agents/ownerContact.js.
• Batched owner lookup for agent list responses to avoid per-agent DB queries.
• Ensured update/avatar/action/revert responses include consistent contact data.
• Added reusable AgentContact frontend rendering.
• Shows contact in:
  • selected-agent landing state
  • agent detail dialog
  • agent marketplace cards
• Renders No contact available when neither support nor owner contact exists.
• Removed client-side cache fallback preservation now that server responses are consistent.

Change Type

Please delete any irrelevant options.

• New feature (non-breaking change which adds functionality)

Testing

Tested on local machine and in a prod like test env.

Checklist

Please delete any irrelevant options.

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• My changes do not introduce new warnings
• I have written tests demonstrating that my changes are effective or that my feature works
• Local unit tests pass with my changes

Peter Rothlaender ginkgo.rothlaender@external.daimlertruck.com on behalf of Daimler Truck AG.
Provider & Legal Notice | Daimler Truck
Copyright (c) {2026} Daimler Truck AG

[peeeteeer]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Keep them coming!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".