Is there an existing issue for this?
Describe the bug
On Linux, aspire agent init cannot detect an App-only GitHub Copilot installation when the official AppImage is launched directly without desktop integration.
GitHub Copilot App detection currently relies on either:
AI_AGENT=github_copilot_app_agent, available while running inside an App session; or
- a GitHub Copilot
.desktop entry in an XDG applications directory.
A directly launched AppImage does not necessarily install a .desktop entry, and a normal terminal does not inherit the App runtime marker. In that case, if Copilot CLI is also absent, aspire agent init does not detect Copilot and skips the shared MCP, skills, and telemetry-hook configuration.
Expected Behavior
App-only Linux users should have a supported way for aspire agent init to recognize or explicitly select their GitHub Copilot installation outside an active App session.
If the App creates a reliable persistent marker, Aspire should use it. Otherwise, consider an explicit configuration/override mechanism and document the portable-AppImage limitation rather than scanning arbitrary filesystem locations.
Steps To Reproduce
- Download and run the official GitHub Copilot AppImage on Linux without installing a
.desktop entry.
- Ensure the standalone Copilot CLI is not installed.
- Open a normal terminal where
AI_AGENT and COPILOT_CLI are unset.
- Run
aspire agent init.
- Observe that GitHub Copilot App is not detected and shared Copilot configuration is skipped.
Exceptions (if any)
N/A
Aspire doctor output
N/A — this is an installation-discovery limitation rather than a missing Aspire prerequisite.
Anything else?
This limitation was identified while testing #19820:
Users who also have Copilot CLI installed are unaffected because the shared Copilot configuration is applied through CLI detection.
Is there an existing issue for this?
Describe the bug
On Linux,
aspire agent initcannot detect an App-only GitHub Copilot installation when the official AppImage is launched directly without desktop integration.GitHub Copilot App detection currently relies on either:
AI_AGENT=github_copilot_app_agent, available while running inside an App session; or.desktopentry in an XDG applications directory.A directly launched AppImage does not necessarily install a
.desktopentry, and a normal terminal does not inherit the App runtime marker. In that case, if Copilot CLI is also absent,aspire agent initdoes not detect Copilot and skips the shared MCP, skills, and telemetry-hook configuration.Expected Behavior
App-only Linux users should have a supported way for
aspire agent initto recognize or explicitly select their GitHub Copilot installation outside an active App session.If the App creates a reliable persistent marker, Aspire should use it. Otherwise, consider an explicit configuration/override mechanism and document the portable-AppImage limitation rather than scanning arbitrary filesystem locations.
Steps To Reproduce
.desktopentry.AI_AGENTandCOPILOT_CLIare unset.aspire agent init.Exceptions (if any)
N/A
Aspire doctor output
N/A — this is an installation-discovery limitation rather than a missing Aspire prerequisite.
Anything else?
This limitation was identified while testing #19820:
Users who also have Copilot CLI installed are unaffected because the shared Copilot configuration is applied through CLI detection.