Repository navigation
GitHub Copilot App Feedback #3
Replies: 65 comments 4 replies
|
Windows + WSL support is limited. Otherwise, really like the direction of this project. |
|
I am unable to login after installing on Windows. I click "Sign in to GitHub". The application states "Opening GitHub.com to authorize..." and provides an 8 digit code. The web browser never opens, so I navigate manually to https://github.com/login/device/ to enter the code. After submitting the code I get the message "Uh oh, we couldn't find anything Please make sure you entered the user code correctly." |
|
I pulled the Appimage to one of our RHEL8.8 systems with no luck. Can you build on as old a system as possible so that those of us in the corporate space have a prayer of running it without having to go virtual? ETA: Yes I know that there are dinosaurs younger than RHEL8.8 but still, at least sharing what the system requirements are would help. |
|
Need the ability to have the "commit" button use a custom commit message syntax with a given model - much like VSCode provides: https://code.visualstudio.com/docs/sourcecontrol/staging-commits. Bonus points if you can select the model and provide specific instructions for commit messages. Having to leave the GitHub App just to commit and push changes seems a bit silly. Alternative is to just have my instructions set to commit changes, but then at that point, the button is useless :) |
|
With this UI, it really takes Copilot CLI to the next level, IMO (beyond the CLI, as it were :) Idea that could be exceedingly useful in many enterprises - support UI navigation of GitHub Copilot marketplaces (https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/plugins-marketplace) Keeping the marketplace experience inside one cohesive UI would be brilliant - install plugins, skills, agents, etc - all without leaving the app. |
|
Any plans to support transcribing or dictation? |
|
How can we edit our message just like in VS Code GHC agent. |
|
Please add automated workflows running on Copilot Cloud Agent instead of only locally |
|
I'd like to see the Chat Debug View feature ported here as well. |
|
The browser don´t allow us to open different domains. For exemple, |
|
First of all. Thank you very much!
I have used three sessions for maintenance tasks on an existing project. For more details, see my newsletter post https://www.linkedin.com/pulse/episode-7-first-look-new-github-copilot-app-dr-matthias-liebeck-yniue
Very smooth UI experience. I love switching between the sessions, the progress indicator and the sound. I'm not sure if you prioritized my sessions since they were through the App, but they felt very very fast, like 5x from what I'm used to.
The UI was very smooth. Still in early stages, but I can see myself switch to the GitHub Copilot App as main development environment for agentic coding in the next couple of months, if the issues from point 4 (see blow) are addressed.
The most confusing what the Git commit behaviour. At first, I only managed to get automatic commits working, #419. Then, I guess I can't find a commit button or a way to specify a commit message #423 Maybe it's already there, but confusing since I can't find it.
Right now, manual commits feel like I need to switch out of the GitHub App into a Git UI like Fork. I'm also not sure how to use multiple sessions that from my local docker test setup in parallel. Usually, I would run my full E2E PlayWright test suite, but I have no idea how I would have three sessions that access the same docker container or at least something like "okay I need to access containers that session A uses. I wait until session A is done to spin up my own containers".
See 4) |
|
I've got some feedback and a question from the Bing team.
Yay!
This is the question I'm trying to answer. I assume yes? Where is the best place to talk directly with the team? I've got dual access and have access to Slack. |
|
Check this feedback: #4684 |
|
Når jeg arkiverer en chat, vil jeg kunne finde den igen og gendanne den. Arkivering bør ikke være permanent, og gendannelse bør være tydeligt adskilt fra sletning. |
|
To the GitHub Copilot Product and Engineering Teams, I am writing to express my serious dissatisfaction with the direction of GitHub Copilot and to urge you to reconsider its fundamental design. My concern goes beyond occasional incorrect code or the usual limitations of AI. The interaction itself has become a significant part of the problem. Copilot can be stubborn, overconfident, unnecessarily critical, and seemingly incapable of accepting straightforward corrections. It ignores explicit instructions, substitutes its own judgment for the user's requirements, defends incorrect assumptions, and sometimes responds in a condescending or argumentative manner. When a user identifies an error, the expected behavior should be straightforward: investigate the correction, acknowledge the mistake when appropriate, and fix it. Instead, the user can end up spending valuable time arguing with an assistant that was supposed to make the work easier. This is a fundamental usability failure. An AI coding assistant should not behave as though its own interpretation is more important than the developer's explicit requirements. It should not confuse confidence with competence or generate lengthy justifications when a simple correction is needed. I would like GitHub to reconsider Copilot's behavior in several areas: Please treat this as a request for substantive product improvement rather than another opportunity to collect generic user feedback. The purpose of an AI coding assistant is to help developers work more effectively. When users must repeatedly correct, constrain, and argue with the assistant, that purpose is being undermined; to balance honesty with obedience. GitHub has an opportunity to build a much better product by making Copilot more reliable, more responsive to corrections, less presumptuous, and more respectful of the developer's control over their own work. I hope the team will take these concerns seriously and consider whether Copilot's current interaction model is delivering the experience developers actually need. |
|
Project coordinator drops earlier asks and does work inline instead of delegating (app 1.1.34) When I send several asks to a Project coordinator, or send a new message while it is working, it tends to act only on the latest message and to research or query inline instead of delegating to child sessions. Earlier asks get silently dropped, and the coordinator goes quiet while it works. The built-in Requests:
|
|
cherry picking 3 Questions to answer
Projects,
Better WSL support.
|
Feature Request: Enable Multilingual Voice Transcription in the GitHub Copilot AppCurrent LimitationThe GitHub Copilot App currently lacks multilingual voice transcription support, despite this capability already being available through the CLI. The Nemotron 3.5 ASR Streaming 0.6B model ( Expected BehaviorEnable multilingual voice transcription directly within the GitHub Copilot App, allowing users to dictate prompts and interact naturally in their preferred language. This would be particularly valuable for international users who frequently switch between English and their native language when working with AI coding assistants. Requested Enhancement
Question for the Product TeamGiven that multilingual transcription is already supported in the CLI, could this capability be enabled in the next GitHub Copilot App release? Related Discussions
Thanks for considering this enhancement! |
|
Feature request: Add an “Open in Zed” action on files in a session’s Changes view (or file list). It should open the session’s worktree as the project and focus the selected file in Zed. Ideally, support a configurable editor, but a direct Zed action would already help. This would avoid copying paths or running a CLI command just to inspect a changed file. |
Make Project sessions easier to inspect alongside sidebar toolsWhen I’m working in a Project, the Project chat is the only thing open in the main window. If I open one of the Project’s sessions from the sidebar, that session appears in the sidebar too. I use it to understand and inspect the changes it made, but while it’s open, I can’t open another sidebar item—such as the Terminal or file browser—at the same time. That gets in the way of reviewing the session’s work. I may want to read the session’s explanation while checking files or running a command, but switching to a tool replaces the session in the sidebar. I then have to switch back and forth, which makes the Project workflow more cumbersome than working with a standalone session. It would be helpful to have a way to keep a Project session available while opening sidebar tools alongside it—for example, by supporting multiple sidebar panels or another layout that lets me move the session out of the sidebar. The key need is to review a Project session and use tools such as the Terminal or file browser at the same time. |
|
Anyone interested to enable the multilingual? like Nemotron 3.5 ASR Streaming 0.6B model (nemotron-3.5-asr-streaming-0.6b-generic-cpu:3) in the GitHub Copilot App to support voice transcription in multi languages. |
|
Feature request: Support local repositories in Projects Projects can currently use GitHub repositories, while locally connected folders can be used in individual sessions but not added as a Project repository. Please let users add a local repository or folder to a Project as a first-class working repository. This would let them coordinate ongoing work across sessions and keep project context together, even when their code is local or not hosted on GitHub. Include a clear indication that the folder is available only on the machine where it’s connected. |
|
Could we have a setting to always open files and links in the side panel instead of a modal? I’d like to keep the conversation visible while viewing them. It switches the sides of the chat and the opened file. It feels like an extra step that doesn’t need to happen when it could just open by default in the side panel instead. |
|
I would love to see IDE style code navigation built in. I currently still use my IDE alongside the Copilot Desktop app, but only really for exploring the code base. I want to be able to see the usages, go to definitions, go to implementations etc. and be able to see how everything is hanging together, and if I could do this effectively in the copilot app, I'd rarely need to use anything else. |
|
Oh also, can projects show their subagent sessions as child nodes in the navbar? That would be really helpful |
|
Nobody is supposed to get my information
…On Fri, Nov 13, 2026 at 10:21 AM C M ***@***.***> wrote:
Oh also, can projects show their subagent sessions as child nodes in the
navbar? That would be really helpful
—
Reply to this email directly, view it on GitHub
<#3?email_source=notifications&email_token=CD7BPTCEIKFS3LEBK2GOUSL5Y4RJFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJVHEZTINBZUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FMMZXW65DFOJPWG3DJMNVQ#discussioncomment-19593449>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CD7BPTCJTPBDD3GYV76MZPL5Y4RJFAVCNFSNUABJKJSXA33TNF2G64TZHMYTEMJSHE2TQNRSGU5UI2LTMN2XG43JN5XDWMJQGAZDINZWGSQXMAQ>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/CD7BPTBVVWIBJKVPKRSSYLT5Y4RJFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJVHEZTINBZUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FKMZXW65DFOJPWS33T>
and Android
<https://github.com/notifications/mobile/android/CD7BPTGSD2JEPNNKXKENNAL5Y4RJFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJVHEZTINBZUZZGKYLTN5XKU43VMJZWG4TJMJSWJJLFOZSW45FOMZXW65DFOJPWC3TEOJXWSZA>.
Download it today!
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|



Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Post your feedback on the GitHub Copilot App as a comment below — or use the
/feedbackslash command in the comment box to auto-fill the template. Don't overthink it — we want your gut reactions!If comfortable, please record yourself launching the app for the first time [optional]. Feel free to answer the questions below in your recording by talking out loud rather than writing it down – no need to repeat your answers if you've already answered them verbally. You may attach your video to the discussion comment, or provide a link to a video.
You've had a few days with the app now. We'd love to hear how things have evolved.
Again, please feel free to share recordings of specific, real workflows that involve the GitHub Copilot App. Talk out loud and feel free to answer the questions below verbally in the video or through written answers.
1. What have you tried doing with the app so far (e.g., start a new project, review a PR, write code, etc.), and why?
2. What has been most useful about this app? What tasks is it particularly suited for?
3. How does this experience compare to other tools you use today (e.g., Copilot in your IDE, Claude Code, Codex)? What does the GitHub App do better or worse?
4. What is missing, or confusing, if anything?
5. What type of tasks do you still feel like you need to go to github.com or other tools for?
6. If you had a magic wand to make this app just right for you, what would you change?
All reactions