Repository navigation
Replies: 1 comment 1 reply
|
In a 1.0 manifest, client-specific data goes under "extensions": {
"com.github.copilot": {
"logo": "assets/preview.png"
}
}The only written requirements are for canvas extensions in CONTRIBUTING.md: the path must be exactly For the Awesome Copilot listing, the mobile-use entry in
|
Uh oh!
There was an error while loading. Please reload this page.
I'm working on mobile-use, a plugin with an MCP server and a skill. What is the supported way for plugin authors to provide a custom plugin icon in GitHub Copilot App, including for plugins listed in Awesome Copilot?
I noticed that the Azure DevOps plugin manifest declares
"logo": "assets/azure-devops.svg", but I couldn't find alogofield in the Agent Plugins 1.0 schema. Is there a supported equivalent for Agent Plugins 1.0, or islogospecific to a legacy format or particular Copilot surface? Are there any requirements for the image format or path?Separately, mobile-use advertises an MCP server icon via
serverInfo.icons, but I don't see it in Copilot App. Is that metadata supported by the app?I also asked in #6345. Thanks for any guidance or documentation!
All reactions