Short summary
The Copilot app's integrated assistant cannot readily determine the desktop app version when filing a bug report.
Affected version or release
1.1.24.0, manually supplied by the user from the Windows executable version details after the initial report. Observed on Windows on 2026-10-02.
Installation context
GitHub Copilot desktop app on Windows, using the integrated chat assistant to investigate a problem and submit a GitHub issue.
What happened?
When the user asked the integrated assistant to file an automation bug, the initial report said:
Exact desktop app build not collected. Observed on 2026-10-02.
The bug-report template asks for the affected app version, but the assistant did not obtain that information through its app tools or provided context.
This leaves a report generated from inside the app without a basic piece of diagnostic metadata. The user should not have to manually look up and transcribe the version for an assistant that is already running inside that app.
This observation establishes a gap in the assistant-driven reporting workflow; it does not establish that the app has no version display elsewhere in its UI.
Steps to reproduce
- Open the Copilot desktop app's integrated chat.
- Ask the assistant to investigate an app problem and submit a bug report.
- Inspect the affected-version field in the generated report.
- In the observed report, the assistant could not supply the desktop app version and used "Exact desktop app build not collected" instead.
Expected behavior
Expose the actual desktop app version and build identifier through a supported app-info tool or assistant context, so the assistant can include them in bug reports without guessing or asking the user to find them manually.
Clearly distinguish the desktop app version from versions of bundled components such as Copilot CLI, GitHub CLI, or the assistant runtime.
Ideally, assistant-generated bug reports should automatically include the app version, OS version, and relevant non-sensitive build/channel metadata.
Additional context
The report that exposed this gap: #4385.
The user subsequently obtained version 1.1.24.0 manually from the Windows executable's Properties > Details. Both reports were updated with that version.
No independent attempt to reproduce this across app versions was made.
Short summary
The Copilot app's integrated assistant cannot readily determine the desktop app version when filing a bug report.
Affected version or release
1.1.24.0, manually supplied by the user from the Windows executable version details after the initial report. Observed on Windows on 2026-10-02.
Installation context
GitHub Copilot desktop app on Windows, using the integrated chat assistant to investigate a problem and submit a GitHub issue.
What happened?
When the user asked the integrated assistant to file an automation bug, the initial report said:
The bug-report template asks for the affected app version, but the assistant did not obtain that information through its app tools or provided context.
This leaves a report generated from inside the app without a basic piece of diagnostic metadata. The user should not have to manually look up and transcribe the version for an assistant that is already running inside that app.
This observation establishes a gap in the assistant-driven reporting workflow; it does not establish that the app has no version display elsewhere in its UI.
Steps to reproduce
Expected behavior
Expose the actual desktop app version and build identifier through a supported app-info tool or assistant context, so the assistant can include them in bug reports without guessing or asking the user to find them manually.
Clearly distinguish the desktop app version from versions of bundled components such as Copilot CLI, GitHub CLI, or the assistant runtime.
Ideally, assistant-generated bug reports should automatically include the app version, OS version, and relevant non-sensitive build/channel metadata.
Additional context
The report that exposed this gap: #4385.
The user subsequently obtained version 1.1.24.0 manually from the Windows executable's Properties > Details. Both reports were updated with that version.
No independent attempt to reproduce this across app versions was made.