microsoft / microsoft/foundry-dev-tools

Failed to list hosted agents for foundry model

Open
#777 1 comment 0 reactions 1 assignee View on GitHub

@hund030 is already working on this.

Since Sep 15, 2026.

Dominant language
JavaScript
Stars
2.1k
Forks
260
Avg merge
42m
Merged PRs (30d)
29

Description

Does this occur consistently? Yes
Repro steps:

  1. when I was working with copilot and I was using my foundry model to generate code it stops working with error and ask me to sign in
  2. I check my status I am login but all i can see the foodery project and can select and switch between them but cannot see any off my model
  3. I restart vs code and still the same cannot accessing my model
  4. I switch to azure extension I can see my resource select between my subscription I am login but cannot see any off my model when switching to foundry extension

Action: l.getChildren
Error type: c
Error Message: Failed to load Hosted Agents (Preview) for project : Failed to list hosted agents for project : You are not signed in to an Azure account. Please sign in.

Version: 1.6.12
OS: win32
OS Arch: x64
OS Release: 10.0.26100
Product: Visual Studio Code
Product Version: 1.137.0
Language: en
UTC time: Sat, 12 Sep 2026 23:32:20 GMT

Call Stack
o.loadChildrenOnce extension.js:2418:61002
async o.loadUntilCurrent extension.js:2418:60391
async o.loadChildren extension.js:2418:60205
async o.getChildren extension.js:2418:59777
extension.js:2160:11354extension.js:2160:11354
async o extension.js:1908:19265
async o.<anonymous> extension.js:2160:11298
async a extension.js:5556:132227
async m.getFoundryAgentEntries extension.js:5556:134803
async m.getChildren extension.js:5556:134220
async r._fetchChildrenNodes extensionHostProcess.js:672:107752
async r.getChildren extensionHostProcess.js:672:103210
async wR.$getChildren extensionHostProcess.js:672:97625
en midle for using not

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.