Describe the bug
Extensions loaded via the extension runtime (visible via extensions_manage list) are not shown in the /env output. This means the AI agent cannot discover available extensions from the environment summary and may fall back to inferior tools (raw API, CLI) when a purpose-built extension is already running.
Expected: /env should include an "Extensions" section alongside MCP Servers, Skills, and Plugins.
Version: 1.0.51
Affected version
GitHub Copilot CLI 1.0.51
Steps to reproduce the behavior
copilot --experimental --yolo
/env
Expected behavior
/env should include an "Extensions" section
Additional context
from copilot:
❯ if it is not listed, would you be able to discover them?
● Yes — I can proactively call extensions_manage with operation: "list" at any time to discover what's loaded. I just didn't do it in this case.
The honest gap: my instructions say "prefer the custom agent if both a built-in and custom agent could handle a task" — but that only triggers if I know a custom tool exists.
Without /env surfacing extensions, I have to remember to call extensions_manage list myself as a discovery step.
I should add this to my habit: when a task involves external systems (JIRA, Confluence, GitHub, etc.), check extensions_manage list first before falling back to raw API or CLI tools. I'll do that going forward in this session.
Describe the bug
Extensions loaded via the extension runtime (visible via extensions_manage list) are not shown in the /env output. This means the AI agent cannot discover available extensions from the environment summary and may fall back to inferior tools (raw API, CLI) when a purpose-built extension is already running.
Expected: /env should include an "Extensions" section alongside MCP Servers, Skills, and Plugins.
Version: 1.0.51
Affected version
GitHub Copilot CLI 1.0.51
Steps to reproduce the behavior
copilot --experimental --yolo
/env
Expected behavior
/env should include an "Extensions" section
Additional context
from copilot:
❯ if it is not listed, would you be able to discover them?
● Yes — I can proactively call extensions_manage with operation: "list" at any time to discover what's loaded. I just didn't do it in this case.
The honest gap: my instructions say "prefer the custom agent if both a built-in and custom agent could handle a task" — but that only triggers if I know a custom tool exists.
Without /env surfacing extensions, I have to remember to call extensions_manage list myself as a discovery step.
I should add this to my habit: when a task involves external systems (JIRA, Confluence, GitHub, etc.), check extensions_manage list first before falling back to raw API or CLI tools. I'll do that going forward in this session.