Blog Post

Microsoft Developer Community Blog
7 MIN READ

πŸš€ Foundry Toolkit for VS Code β€” July 2026 Update

junjieli's avatar
junjieli
Icon for Microsoft rankMicrosoft
Jul 31, 2026

July was a clean-up-and-level-up month. Four releases shipped for the Foundry Toolkit for VS Code: 1.6.3, 1.6.4, 1.6.5, and 1.6.6.

The theme this month wasn't a single headline feature β€” it was making the extension feel like one coherent workspace instead of a pile of tree nodes. Your Foundry resources got flattened and consolidated into tabbed pages. The Tool Catalog learned to add tools without making you leave the page. Agent Inspector started showing you every event your agent emits. And a brand-new Agent Optimization (preview) turned "tweak the prompt and hope" into a measured, compare-and-deploy loop.

Have feedback or hit a bug? File an issue on GitHub β€” the roadmap moves on what you tell us.

Highlights

  • Agent Optimization (preview) β€” optimize a Hosted Agent straight from the playground, compare generated candidates against the baseline, inspect the scores, and deploy the winner.
  • A flatter, tabbed workspace β€” Models, Agents, Tools, Knowledge, and Evaluations now live at the root under My Resources, with consolidated Models and Knowledge pages instead of endless nested nodes.
  • Tool Catalog that works inline β€” add a tool to an agent or toolbox, see what's already connected, and provision ready-made Essentials and WorkIQ Suite toolbox templates in one click.
  • Agent Inspector Events tab β€” every parsed Responses event, including function calls and their results, not just a summary.
  • Model management from the row β€” view code, copy the key or endpoint, edit, or delete a deployment without a detour; search the model list right when you deploy.

🧭 One workspace, not a maze of tree nodes

You open the extension to do one thing β€” deploy a model, check an agent β€” and instead you're expanding node after node to find it. That friction is gone.

In 1.6.4, your Foundry resources got flattened. Models, Agents, Tools, Knowledge, Evaluations, and Classic now sit directly at the view root under My Resources β€” not buried beneath the project. Project-level actions moved into a tidy settings menu, and the redundant Connected Resources node is gone. The tree also stays flat and stable while Foundry loads, instead of briefly nesting everything under a temporary wrapper.

The consolidation runs deeper than the sidebar. Over 1.6.3 and 1.6.4, the Models and Knowledge nodes stopped expanding into nested items and became real tabbed webviews:

  • Models β€” a searchable page with a Foundry tab for your hosted deployments, an Others tab for connected GitHub, NVIDIA NIM, OpenAI, Anthropic, Google, and custom-provider models, and a Catalog tab that opens the Model Catalog in place.
  • Knowledge β€” an Indexes tab (vector stores plus project-managed Azure AI Search, Managed Azure AI Search, and CosmosDB indexes) and a Knowledge Bases tab for Azure AI Search knowledge bases.

Resource lists got a consistency pass too: Prompt Agents, Hosted Agents, Routines, Workflows, and Models are now ordered newest-first, and the Evaluations list adopted the shared resource-list layout β€” so search, tables, spacing, and pagination behave the same everywhere.

🧩 Models β€” deploy and manage without the detour

You picked a model. Now you just want to ship it and grab its endpoint β€” not click through three screens.

Model management moved onto the row itself in 1.6.5. For Foundry models you can view code, copy the API key or endpoint, edit, or delete a deployment right there. For Others models you can load one into Agent Builder, copy its name, edit its API key, delete it, or open its model card when available.

Deployment itself got sharper in 1.6.6: search the model list instead of scrolling, keep your Model Catalog selection prefilled, and get inline validation before you deploy β€” with capacity details that stay aligned to whatever you last picked. And if you live in Azure OpenAI, 1.6.4 added a Copy Azure OpenAI Endpoint action to the project settings menu so the URL is one click away.

The Model Catalog also refreshed its featured lineup and the ordering of collapsed Microsoft Foundry models.

πŸ”§ A Tool Catalog you don't have to leave

Wiring tools onto an agent used to mean bouncing between pages. Now the Tool Catalog does the work where you're already standing.

1.6.3 made it inline: add a tool to a prompt agent or a toolbox β€” and even create a new toolbox β€” without leaving the catalog. Catalog tools now show whether they're already connected, so you're not guessing at duplicates.

The bigger time-saver is toolbox templates. Two ready-made ones β€” Essentials and WorkIQ Suite β€” show up in the Toolboxes section with a read-only preview (tools and skills grouped), and one-click provisioning creates the required connections and skills, then pre-fills the create-toolbox form. In 1.6.5, the Tools page also gained a Catalog tab so you can jump straight into the catalog from your tools overview.

πŸ€– Hosted Agents β€” smoother from first sample to deploy

The first minute of a new agent sets the tone, and the last minute β€” the deploy β€” is where confidence is won or lost.

Creating a Hosted Agent got friendlier in 1.6.6: the sample gallery now uses a responsive two-column layout with filters on the right, starts with the Agent Framework Hello World sample already selected, and lets you continue straight from the card you chose. Earlier, 1.6.3 added short, Microsoft Learn–grounded descriptions (with Learn more links) to each agent tab β€” Prompt Agent, Hosted Agent, Routines, and Workflow β€” so first-timers can tell the types apart, plus a dedicated write-up for the Invocations (WebSocket) protocol that highlights real-time voice and bidirectional streaming over a single persistent connection.

Deploy tightened up across the month:

  • Remote package mode is now the recommendation (1.6.5). If a bundled code deployment fails, you can reopen the form with remote package mode already selected β€” no starting over.
  • Unified `azure.yaml` (1.6.3) β€” the container-deploy schema now matches the unified Azure Developer CLI (azd) payload with protocol_versions and a top-level container image.
  • Clearer messages β€” an actionable "package too large" (250 MB) error for code deploys, and an invoke-playground request-body placeholder that actually shows the shape: {"input": "your message"}.

The remote playground grew up too: it now renders the OAuth consent card so OAuth-gated tools can run β€” with a resume step after you authorize β€” and log streaming starts when you open the Logs tab instead of firing requests before the stream is even ready.

πŸ” Agent Inspector β€” see every event, not a summary

Debugging an agent from a summary is like debugging code from a stack trace with the middle cut out. You need the whole sequence.

1.6.6 gave the Agent Inspector Details view a complete Events tab: every parsed Responses event, including function calls and their results, laid out in order. The Tools tab stays as the summarized view when that's all you need β€” so you can zoom out or drill all the way in. And since 1.6.3, azd ai agent run opens the Agent Inspector inside VS Code instead of kicking you out to an external browser.

🎯 Agent Optimization β€” tuning you can measure

Prompt tuning is usually vibes: change a line, run it a few times, convince yourself it's better. 1.6.4 replaces the vibes with a loop.

Agent Optimization (preview) lets you optimize a Hosted Agent right from the playground. It generates candidate configurations, compares each one against your baseline, and shows you the scores and the exact configuration changes behind them β€” so you can see *why* a candidate wins, not just that it does. When one earns it, you deploy the best candidate straight from the comparison. Tuning becomes a decision you can defend.

πŸͺ² Fixes and polish

  • Hosted Agent Deploy β€” deployments no longer run unnecessary access setup when your existing Foundry permissions already allow it (1.6.5); ADC/vNext agents advertising protocol version 2.0.0 are no longer misclassified and blocked; and environment variables authored in the azure.yaml list form are no longer silently dropped (1.6.3).
  • Hosted Agent Playground β€” OAuth consent no longer leaves an empty agent response above the card (1.6.5); the Copilot SDK Python template now runs on Windows instead of failing on a missing /home path; and overlapping conversation resets are latest-wins, preventing stale state and empty conversation IDs (1.6.4).
  • Model Catalog β€” restored the missing logos for Gemma, Kimi, Ministral, and Nemotron (1.6.5).
  • Resource lists β€” canceling a delete no longer removes the row; lists now reflect the host's actual state (1.6.3).
  • Tool Catalog β€” custom connection cards for Remote MCP, OpenAPI, and A2A stay visible when you're signed out; the Tools webview tab now shows its icon consistently (1.6.4, 1.6.5).
  • Startup β€” background data warm-up errors no longer pop open the Output panel during activation (1.6.4).

⚠️ Deprecation

  • Foundry Local models are no longer offered as GitHub Copilot Chat language model providers (1.6.5). If you were selecting a Foundry Local model as a Copilot Chat provider, pick a different model provider in the Copilot Chat model picker β€” Foundry Local still works everywhere else in the toolkit, including the playground and Agent Builder.

πŸš€ Get it and tell us what to build next

Everything above is one update away.

This month was about clearing the clutter between you and your agents β€” a flatter workspace, inline tooling, deeper inspection, and optimization you can actually measure. Try Agent Optimization on your next Hosted Agent, and let us know what earns a spot in the August update.

Happy building. πŸš€

Updated Jul 31, 2026
Version 1.0
No CommentsBe the first to comment