Unable to open Foundary Project In VS Code
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- azure, javascript, vscode
- Domain
- developer-experience
Research direction
Start by tracing the Foundry agent tree's getChildren and getFoundryAgentEntries calls shown in the stack trace, then follow loadChildrenOnce and loadUntilCurrent in the extension code. The report points to a missing Azure OpenAI connection, but gives no reproduction steps or expected behavior; determine how this error should be handled and verify the fix against a project without that connection.
Written by the indexing model from the issue text.
Description
Does this occur consistently?
Repro steps:
Action: i.getChildren
Error type: c
Error Message: Failed to load Prompt Agents for project azure-ai-project-for-agents: 400: No Azure Open AI connection associated with this project. Please add a connection in AI studio.
Version: 1.6.15
OS: win32
OS Arch: x64
OS Release: 10.0.26200
Product: Visual Studio Code
Product Version: 1.137.0
Language: en
UTC time: Thu, 08 Oct 2026 05:08:41 GMT
Call Stack
a.loadChildrenOnce extension.js:2418:61196
a.loadUntilCurrent extension.js:2418:60585
extension.js:2158:22927extension.js:2158:22927
a.loadChildren extension.js:2418:60399
a.getChildren extension.js:2418:59934
extension.js:2160:13444extension.js:2160:13444
o extension.js:1908:19248
a.<anonymous> extension.js:2160:13388
a extension.js:5568:132224
m.getFoundryAgentEntries extension.js:5568:134800
m.getChildren extension.js:5568:134217
r._fetchChildrenNodes extensionHostProcess.js:672:107752
r.getChildren extensionHostProcess.js:672:103210
wR.$getChildren extensionHostProcess.js:672:97625
- Dominant language
- JavaScript
- Stars
- 2.1k
- Forks
- 260
- Avg merge
- 10h 48m
- Merged PRs (30d)
- 34
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/foundry-dev-tools
-
needs attention
Difficulty 4/5 3-5 days Newbie friendliness 12/100
microsoft/foundry-dev-tools#851 · 1 comment ·
Maintainers usually reply within 1 day
-
needs attention
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/foundry-dev-tools#850 · 1 comment ·
Maintainers usually reply within 1 day
-
needs attention
Difficulty 3/5 1-2 days Newbie friendliness 38/100
microsoft/foundry-dev-tools#849 · 1 comment ·
Maintainers usually reply within 1 day
-
errorOpenneeds attention
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/foundry-dev-tools#847 · 1 comment ·
Maintainers usually reply within 1 day
-
testOpenneeds attention
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/foundry-dev-tools#846 · 1 comment ·
Maintainers usually reply within 1 day
All issues in microsoft/foundry-dev-tools
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
jspreadsheet/ce#1809 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
githubnext/gh-aw-workshop#4458 ·
Maintainers usually reply within 1 day
-
Add: CartoonitoOpencheck:failed feeds:add
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
iptv-org/database#37390 · 1 comment ·
Maintainers usually reply within 9 days
-
bug: directory index route root priority is overwritten when wildcard is falsePossibly taken @TalhaHunter101 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
fastify/fastify-static#617 ·
-
bug confirmed css v6
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day