Feature Request: Associate Custom Agents with Projects

Summary

Allow users to associate one or more custom agents with a ChatGPT Project so those agents are immediately visible and accessible whenever the project is opened.

This would create a natural relationship between Projects and Agents, making Projects the central workspace for long-term development efforts.

Problem

The Agent Library is an excellent place to create and manage custom agents.

However, once an agent is created, there is currently no way to associate it with the project it was built to support.

As projects grow, users often create multiple specialized agents dedicated to a single project.

Examples:

  • Steward
  • CTO
  • Security Officer (CISO)
  • Builder
  • Documentation Writer
  • QA Reviewer
  • Research Assistant

When returning to a project days or weeks later, users must leave the Project, open the Agent Library, and manually locate the correct agent.

For users managing multiple projects and dozens of custom agents, this becomes increasingly difficult.

Proposed Solution

Add an Assigned Agents section to every Project.

Projects would continue organizing conversations and files, while also displaying the agents specifically assigned to that project.

For example:

Project: InvestorOS

──────────────────────────

Chats

Files

Knowledge

Assigned Agents

• Steward
• CTO
• Security Officer
• Builder
• Documentation Writer

Selecting an agent would immediately launch a conversation with that agent while maintaining the context of the current project.

Why This Matters

Projects already serve as the organizational hub for conversations and files.

Allowing Projects to also organize the custom agents created for them would complete the workflow and significantly reduce friction.

Rather than treating agents as separate assets that users must remember to find, they become first-class members of the project itself.

Benefits

  • Faster navigation
  • Reduced context switching
  • Easier management of long-term projects
  • Better organization for users with many custom agents
  • More intuitive project workspaces
  • Improved onboarding for collaborators

Example Workflows

Software Development Project

Assigned Agents:

  • Steward
  • CTO
  • Security Officer
  • Builder
  • QA Reviewer

Writing Project

Assigned Agents:

  • Editor
  • Research Assistant
  • Fact Checker
  • Character Designer

Business Project

Assigned Agents:

  • Business Analyst
  • Financial Advisor
  • Marketing Strategist
  • Documentation Assistant

Optional Enhancements

These are not required for the core feature but would make it even more useful:

  • Allow one agent to belong to multiple projects.
  • Assign or remove agents from either the Project page or the Agent Library.
  • Display the projects an agent is assigned to within its settings.
  • Allow users to pin a “Primary Agent” for the project.
  • Support drag-and-drop assignment from the Agent Library.
  • Sort assigned agents by role or custom order.

Why This Is Different from the Existing Agent Library

This request is not asking for a new Agent Library.

The Agent Library already fulfills that role well.

Instead, this feature would establish a relationship between two existing concepts:

Projects already organize:

  • Conversations
  • Files
  • Knowledge

This proposal simply extends that organization to include:

Closing Thoughts

As users increasingly build specialized teams of custom agents, Projects naturally become the place where those agents should live.

Opening a project should immediately answer the question:

“Which agents were created to work on this project?”

Adding project-level agent assignment would make Projects feel like complete workspaces rather than collections of chats and files, while building naturally on functionality that already exists.