Feature Request: Real-Time Collaborative GitHub Copilot Sessions

[deepanman]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot CLI

Body

Feature: Real-Time Collaborative GitHub Copilot Sessions

Problem

Software development is highly collaborative, but GitHub Copilot sessions are primarily designed for one developer at a time. When developers work together—such as during pair programming, debugging, incident resolution, or code reviews—they cannot easily collaborate with Copilot in one shared, real-time session.

Developers must share screens, copy Copilot responses into chat, or separately provide the same context to their own Copilot sessions. This breaks the flow and can produce inconsistent suggestions.

Proposed Feature

Allow a developer to create a shared GitHub Copilot session and invite other authorized developers to join and collaborate live, similar to how multiple people work together in Google Docs.

All participants should be able to:

• View the same Copilot conversation and responses in real time.
• Ask Copilot questions within the shared session.
• Collaboratively edit code with live cursors and participant indicators.
• See who submitted each prompt or made each change.
• Share selected files, terminal output, errors, and repository context with Copilot.
• Accept, reject, or discuss Copilot’s proposed changes.
• Add comments or annotations to Copilot-generated code.
• Hand control of the session to another participant.
• Keep a searchable transcript of prompts, responses, decisions, and code changes.

Example Workflow

1. A developer encounters a difficult production issue.
2. They start a “Shared Copilot Session” from VS Code or JetBrains.
3. They invite selected team members using GitHub identities or a secure link.
4. Everyone joins the same workspace and sees the same Copilot conversation and approved project context.
5. Team members investigate the issue, ask follow-up questions, and review Copilot’s proposed fix together.
6. The team approves the change and optionally creates a branch, commit, issue, or pull request directly from the session.

Permissions and Security

The session owner should control:

• Who may view, prompt, edit, approve changes, or use the terminal.
• Which files and repository resources are shared.
• Whether secrets, environment files, and sensitive directories are excluded.
• Whether participants can invite additional people.
• Whether the session transcript is retained.
• Whether Copilot may execute commands or modify files.

For organizations, the feature should respect existing GitHub repository permissions, Copilot Business/Enterprise policies, audit logging, data-retention settings, and branch-protection rules.

Why This Is Different

This would go beyond ordinary screen sharing or collaborative editing. The important capability is that every participant and Copilot share the same:

• Conversation history
• Code context
• Agent state
• Proposed changes
• Tool activity
• Decisions and approvals

The experience could integrate with GitHub Codespaces or Visual Studio Live Share, but Copilot would become a shared team participant rather than an assistant visible to only one developer.

Benefits

• Makes AI-assisted pair and mob programming possible.
• Accelerates debugging and incident response.
• Prevents developers from repeatedly explaining the same context.
• Enables teams to review AI-generated changes before applying them.
• Helps junior developers learn from senior developers’ interactions with Copilot.
• Improves governance and traceability for enterprise development teams.

Suggested Name

GitHub Copilot Collaborative Sessions
Alternative: Copilot Live Collaboration

Authored using AI