Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unable to open Foundary Project In VS Code

Open
#848 1 comment 0 reactions 0 assignees View on GitHub

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

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

needs attention

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

  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.

More from microsoft/foundry-dev-tools

All issues in microsoft/foundry-dev-tools

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.