Proposed Feature Request: Support for Multi-Agent Identities (Sub-Bots) for GitHub Apps

[savasp]

Select Topic Area

Product Feedback

Body

Problem Statement:

Currently, GitHub Apps are treated as a single monolithic entity. While an App can perform actions, it cannot be assigned to an Issue or PR. To work around this for AI Agents, developers are forced to create "Machine Users," which consume paid seats and are difficult to manage at scale.

The Use Case: AI Agent Orchestration

I am building infrastructure that exposes a team of specialized AI agents (e.g., a "Security Agent," a "Reviewer Agent," and a "Docs Agent").

• Granular Attribution: I need to assign specific tasks to specific agents within the team so humans know exactly which "agent" is responsible for a PR or Issue.
• Collaborator Status: These agents act as teammates. They need to appear in the assignee dropdown and have their own activity history.
• Scalability: Creating a new GitHub account (Machine User) for every new specialized agent in an AI swarm is a significant administrative and financial hurdle.

Proposed Solution:

Allow GitHub Apps to register "Sub-Identities" or "Agent Members."

1. Assignable Apps: Allow the primary App (or its defined sub-agents) to be added to the assignees list.
2. App-Managed Teams: Let a single GitHub App "spawn" multiple bot identities that appear as collaborators without requiring separate user licenses.
3. Visual Distinction: Use a specific "Agent" or "Bot" badge in the UI to distinguish them from human collaborators.

Why this matters now:

As the industry moves toward Agentic Workflows, GitHub needs a native way to represent AI swarms. Treating every AI agent as a full "Human User" is an outdated model that creates friction for developers building the next generation of automated tooling.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐