fix: include conversation_starters in agent list projection

[inodb]

Summary

• The getListAgentsByAccess query in api/models/Agent.js uses an explicit field projection that was missing conversation_starters
• This meant the field was never returned to the client, so agent conversation starters could never render in the ConversationStarters component — even when correctly set in the database
• Adds conversation_starters: 1 to the projection

Context

The original conversation starters feature (PR #3699) was built for assistants, which use a separate documents endpoint. When agents were added later, the agent list projection was written with a hardcoded field list that never included conversation_starters.

Test plan

• Set conversation_starters on an agent in MongoDB
• Verify the field is returned by GET /api/agents
• Confirm starters render on the landing page when selecting that agent

[Copilot]

Pull request overview

Fixes the agents list API response to include conversation_starters, enabling the client’s ConversationStarters UI to render starters for agents when configured in MongoDB.

Changes:

• Add conversation_starters: 1 to the getListAgentsByAccess Mongo projection so GET /api/agents returns the field.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.