Support Foundry Canvas in VS Code
维护者通常 1 天内回复
@qinezh 已经在做这个了。
开始于 2026年10月13日。
评估
这个 Issue 还没有评估数据。
描述
The microsoft-foundry plugin hard-codes a check for
process.env.AI_AGENT === "github_copilot_app_agent"
This is causing it only to work in the GitHub Copilot App.
As we add Canvas support to VS Code, could you please also allow for VS Code as well?
process.env.AI_AGENT === "github_copilot_app_agent" || AI_AGENT === "github_copilot_vscode_agent"
Verbose AI-generated details below:
Problem
The microsoft-foundry plugin is discovered and synchronized into VS Code Agent Host sessions, but it contributes no canvases because its bundled extension only enables its tools, companion instructions, and canvases when:
process.env.AI_AGENT === "github_copilot_app_agent"
VS Code intentionally identifies its Copilot agent processes as:
github_copilot_vscode_agent
See AiAgentEnvValue in microsoft/vscode.
The host check is visible in microsoft-foundry/com.github.copilot/extensions/microsoft-foundry/extension.mjs: when the check is false, the extension joins the session with an empty canvases array.
Reproduction
- Install the
microsoft-foundryplugin in VS Code. - Enable
chat.canvases.enabled. - Create a new local Copilot Agent Host session.
- Confirm the plugin is enabled and synchronized into the session.
- List available canvases.
The Foundry agent-builder canvas is absent because VS Code supplies AI_AGENT=github_copilot_vscode_agent.
Requested behavior
Please support github_copilot_vscode_agent in addition to github_copilot_app_agent, so the Foundry canvases can be registered in VS Code when the host provides the required Canvas capabilities.
For example, the host admission check could accept both known identifiers, or preferably feature-detect the specific Canvas/RPC capabilities the extension needs. The latter would allow App-specific integrations such as terminal and browser canvases to degrade explicitly if a host does not provide them.
Expected result
With canvases enabled, a new VS Code Copilot Agent Host session discovers the agent-builder canvas and can open it through the normal Canvas extension APIs without changing existing GitHub Copilot App behavior.
🤖 Written by GitHub Copilot on behalf of @jruales.
- 主要语言
- JavaScript
- 星标
- 2.1k
- 派生
- 260
- 平均合并
- 1 天 2 小时
- 30 天内合并 PR
- 31
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoft/foundry-dev-tools 的其他 Issue
-
needs attention
难度 4/5 3-5 天 新手友好度 18/100
microsoft/foundry-dev-tools#870 · 1 条评论 ·
维护者通常 1 天内回复
-
issue未关闭needs attention
难度 3/5 半天 新手友好度 22/100
microsoft/foundry-dev-tools#868 · 1 条评论 ·
维护者通常 1 天内回复
-
needs attention
难度 4/5 3-5 天 新手友好度 22/100
microsoft/foundry-dev-tools#867 · 1 条评论 ·
维护者通常 1 天内回复
-
needs attention
难度 4/5 3-5 天 新手友好度 22/100
microsoft/foundry-dev-tools#864 · 3 条评论 ·
维护者通常 1 天内回复
-
y未关闭needs attention
难度 4/5 1-2 天 新手友好度 18/100
microsoft/foundry-dev-tools#863 · 1 条评论 ·
维护者通常 1 天内回复
查看 microsoft/foundry-dev-tools 的全部 Issue
相似的 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 67/100
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 76/100
SasanLabs/VulnerableApp#836 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
keyxmakerx/Chronicle#1469 ·
维护者通常 1 天内回复
-
Connection.prototype.bulkWrite() with ordered: false resolves null when a write fails可能已有人在做 @maxymlyskov 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
Automattic/mongoose#16601 ·
维护者通常 2 天内回复
-
sandbox-vercel: persistent: false is dropped for live sandboxes created from a template, so every stop writes a snapshot可能已有人在做 @jvg123 今天认领。 未关闭factory-active task-identify-harness-labels-done task-identify-issue-type-done
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复