Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Support Foundry Canvas in VS Code

Aperta
#861 4 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@qinezh ci sta già lavorando.

Dal 13/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

canvas

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

  1. Install the microsoft-foundry plugin in VS Code.
  2. Enable chat.canvases.enabled.
  3. Create a new local Copilot Agent Host session.
  4. Confirm the plugin is enabled and synchronized into the session.
  5. 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.

Lingua principale
JavaScript
Stelle
2.1k
Fork
260
Merge medio
1g 6m
PR unite (30g)
33

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/foundry-dev-tools

Tutte le issue di microsoft/foundry-dev-tools

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.