GitHub Copilot in VS Code Live Share Hosts vs Guests: Behavior Notes

When you use GitHub Copilot inside a Visual Studio Code Live Share session, the experience differs significantly between the host who owns the session and the guests who join it. Many developers assume Copilot works identically for all participants, but it does not. The host’s Copilot subscription, editor settings, and file access determine what suggestions guests see and whether they can generate code at all. This article explains exactly how Copilot behaves for hosts versus guests, what features each role can use, and how to avoid confusion during pair programming sessions.

How GitHub Copilot Works in Live Share Sessions

VS Code Live Share allows multiple developers to collaborate on the same codebase in real time. One person acts as the host and shares their workspace. Guests join the session and can edit files, run terminals, and debug. GitHub Copilot is an AI-powered code completion tool that suggests code as you type. It runs as a VS Code extension tied to an individual’s GitHub account.

In a Live Share session, Copilot does not run independently for each participant. Instead, the host’s Copilot instance generates all suggestions. Guests cannot activate their own Copilot subscription inside the shared workspace. This design prevents licensing conflicts and ensures consistent suggestions across the session. The host must have an active GitHub Copilot subscription for any participant to receive AI-generated code completions.

Prerequisites for Using Copilot in Live Share

Before starting a Live Share session with Copilot, verify these requirements:

• The host must have a GitHub Copilot subscription. Individual, Business, or Enterprise plans all work.
• The host must install the GitHub Copilot extension in VS Code. Guests do not need the extension installed.
• All participants must have VS Code version 1.80 or later. Older versions may not support Copilot in Live Share.
• The host must enable the Live Share extension and start a session. Guests join via an invite link.

Host vs Guest Copilot Behavior: What Each Role Can Do

The table below summarizes the key differences between host and guest capabilities when using Copilot in a Live Share session.

Host Capabilities

The host retains full control over Copilot. They can:

• Receive inline code suggestions as they type. These suggestions appear to both the host and guests in the shared editor.
• Use Copilot Chat to ask questions about the codebase. Chat responses are visible only to the host unless the host shares the output manually.
• Toggle Copilot on or off for the session. Disabling Copilot stops all suggestions for every participant.
• Configure Copilot settings, such as which files to exclude or whether to use public code matches. These settings apply to the entire session.

Guest Capabilities

Guests have limited Copilot access. They can:

• View inline suggestions generated by the host. Suggestions appear in the guest’s editor as the host types.
• Accept or reject suggestions that the host triggers. However, guests cannot generate new suggestions by typing in their own editor.
• Use Copilot Chat only if the host explicitly enables guest chat access. By default, chat is host-only.
• See Copilot status indicators, such as the Copilot icon in the status bar, but cannot change the state.

Steps to Configure Copilot for Live Share Sessions

Follow these steps to set up and use Copilot correctly in a Live Share session. The host must perform the initial configuration.

1. Install the GitHub Copilot extension
   Open VS Code on the host machine. Go to the Extensions view and search for GitHub Copilot. Install the extension published by GitHub. Sign in with your GitHub account that has an active Copilot subscription. Verify the Copilot icon in the status bar shows a solid color, not a grayed-out state.
2. Start a Live Share session
   Click the Live Share icon in the activity bar. Select Start Collaboration Session. VS Code generates a unique invite link. Share this link with your guests. Guests open the link in their browser and join the session through VS Code.
3. Enable Copilot for the session
   Ensure Copilot is active on the host machine. If Copilot is disabled, guests see no suggestions. The host can check the Copilot status by clicking the Copilot icon in the status bar and selecting Enable Completion.
4. Test Copilot as the host
   Open a supported file type such as Python, JavaScript, or TypeScript. Start typing a function or loop. Copilot should display inline suggestions in gray text. Press Tab to accept. Guests in the session see the same suggestion and the accepted code in real time.
5. Allow guest chat access if needed
   Open the Live Share extension settings. Look for Live Share: Guest Chat Access. Set this to true to let guests use Copilot Chat. Without this setting, guests cannot type in the chat panel. Note that chat responses still come from the host’s Copilot subscription.

Common Issues and What to Do When Copilot Behaves Unexpectedly

Guests See No Copilot Suggestions

This is the most frequent complaint. The cause is almost always that the host does not have an active Copilot subscription or the extension is not running. Verify the host’s Copilot status by checking the VS Code status bar. If the icon shows a circle with a line through it, Copilot is disabled. The host must re-enable it. Also confirm that the host is typing in a supported language. Copilot does not suggest code in plain text files or unsupported file types.

Copilot Chat Is Grayed Out for Guests

By default, Copilot Chat is host-only. The host must enable guest chat access in the Live Share settings. Go to VS Code Settings, search for Live Share: Guest Chat Access, and set it to true. Guests must then close and reopen the chat panel. If the setting is already enabled and chat still does not work, ask the host to restart the Live Share session.

Guests Cannot Accept Copilot Suggestions

Guests can only view suggestions triggered by the host. If a guest types code, Copilot does not generate suggestions for that input. This is by design. To let guests generate code, the host can use a workaround: the host types a comment or partial line, triggers a suggestion, and then the guest accepts it. Alternatively, the host can share the keyboard via Live Share’s follow mode, but the host’s keystrokes still control Copilot.

Copilot Suggests Code from the Guest’s File Context

Some users expect Copilot to adapt suggestions based on the guest’s cursor position or file. Copilot uses the host’s editor context, including the open file and cursor location. If a guest scrolls to a different part of the file, the host’s cursor does not move. The host must navigate to the guest’s position for Copilot to generate relevant suggestions. Use Live Share’s focus-follow mode to synchronize cursor positions.

GitHub Copilot in Live Share: Host vs Guest Feature Comparison

Feature	Host	Guest
Inline code suggestions	Full control: generate, accept, reject	View only; cannot generate new suggestions
Copilot Chat	Full access by default	Requires host to enable guest chat access
Copilot subscription required	Yes, active subscription	No, uses host’s subscription
Copilot extension required	Yes, installed and signed in	No, extension not needed
Settings control	Can toggle Copilot on/off, exclude files, set public code preference	Cannot change any Copilot settings
Status indicator visibility	Sees full status and can interact	Sees status icon but cannot change state
Support for multiple languages	Same as standalone Copilot	Same as standalone Copilot, but only host triggers suggestions

This table confirms that the host holds all control over Copilot in a Live Share session. Guests are passive consumers of AI suggestions. To maximize collaboration, the host should communicate clearly when they are about to generate a suggestion and allow guests to guide the typing direction.

Understanding these behavior notes helps teams avoid wasted time troubleshooting. Before a session, confirm the host’s Copilot subscription is active. During the session, use Live Share’s follow mode to keep the host’s cursor aligned with the guest’s focus. For advanced scenarios, consider using a shared cloud environment where each developer has their own Copilot instance, but for ad-hoc pair programming, the host-guest model works reliably when configured correctly.