Copilot (assistive) persistence

[qwerty-uiop-qaz]

Select Topic Area

Product Feedback

Copilot Feature Area

General

Body

GitHub copilot in assistive mode should remain open even after opening a file.

[Akash1134]

Hi @qwerty-uiop-qaz,

Thank you for sharing your feedback about wanting GitHub Copilot's assistive mode to remain open even after opening a file. This is a great suggestion that would improve workflow continuity when navigating between files.

Current Behavior

Currently, in VS Code and other supported editors, the assistive panel automatically closes when you open a new file. This behavior is documented in the official VS Code Copilot documentation, where the assistive mode is designed to work on a per-file basis by default.

Potential Solutions

We're actively exploring enhancements to the assistive mode experience based on user feedback like yours. Here are some current workarounds and planned improvements:

Current Workarounds:

1. Pinning the assistive panel: According to the VS Code Copilot Chat documentation, you can use the "pin" icon in the top right corner of the Copilot panel to keep it open across certain navigation actions.

2. Using keyboard shortcuts: The VS Code documentation notes that you can quickly reopen the assistive panel using keyboard shortcuts as listed in the Copilot keyboard shortcuts reference:

   • Windows/Linux: Ctrl+Enter (mapped to github.copilot.generate)
   • macOS: Ctrl+Return (mapped to github.copilot.generate)

3. Editor layouts: The VS Code workspace layout documentation explains how to set up editor groups that can help maintain visibility of different panels during navigation.

Relevant Settings:

According to the Copilot configuration documentation, there are several settings that might impact this behavior:

github.copilot.editor.enableAutoCompletions
github.copilot.chat.focusAfterInsertion

While there isn't currently a direct setting for maintaining the assistive panel across file navigation, these settings help control related aspects of the Copilot interface behavior.

How You Can Help

If you're interested in tracking Copilot feature updates, the official GitHub Changelog regularly announces new Copilot features and improvements.

Thank you again for taking the time to share this suggestion!

[qwerty-uiop-qaz]

FYI, I noticed this online also.     Sent: Friday, May 23, 2025 at 4:56 AM From: "Akash" ***@***.***> To: "community/community" ***@***.***> Cc: "Qwerty" ***@***.***>, "Mention" ***@***.***> Subject: Re: [community/community] Copilot (assistive) persistence (Discussion #160043)   Hi @qwerty-uiop-qaz, Thank you for sharing your feedback about wanting GitHub Copilot's assistive mode to remain open even after opening a file. This is a great suggestion that would improve workflow continuity when navigating between files. Current Behavior Currently, in VS Code and other supported editors, the assistive panel automatically closes when you open a new file. This behavior is documented in the official VS Code Copilot documentation, where the assistive mode is designed to work on a per-file basis by default. Potential Solutions We're actively exploring enhancements to the assistive mode experience based on user feedback like yours. Here are some current workarounds and planned improvements: Current Workarounds: Pinning the assistive panel: According to the VS Code Copilot Chat documentation, you can use the "pin" icon in the top right corner of the Copilot panel to keep it open across certain navigation actions. Using keyboard shortcuts: The VS Code documentation notes that you can quickly reopen the assistive panel using keyboard shortcuts as listed in the Copilot keyboard shortcuts reference: Windows/Linux: Ctrl+Enter (mapped to github.copilot.generate) macOS: Ctrl+Return (mapped to github.copilot.generate) Editor layouts: The VS Code workspace layout documentation explains how to set up editor groups that can help maintain visibility of different panels during navigation. Relevant Settings: According to the Copilot configuration documentation, there are several settings that might impact this behavior: github.copilot.editor.enableAutoCompletions github.copilot.chat.focusAfterInsertion While there isn't currently a direct setting for maintaining the assistive panel across file navigation, these settings help control related aspects of the Copilot interface behavior. How You Can Help If you're interested in tracking Copilot feature updates, the official GitHub Changelog regularly announces new Copilot features and improvements. Thank you again for taking the time to share this suggestion! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>