The Microsoft Foundry extension for Azure Developer CLI reaches 1.0 and general availability, keeping agent and deployment configuration in azure.yaml next to the code
Defining, locally debugging and deploying a hosted agent now share one CLI and config file that can go through PR review and CI/CD.
// Key points
- The microsoft.foundry extension bundle reaches 1.0 and general availability; it needs Azure Developer CLI 1.37.0 or later
- Agent and deployment configuration lives in azure.yaml with the code, so teammates and CI/CD reuse one definition
- azd ai agent run tests locally, and Agent Inspector shows requests and responses
- A hosted agent runs your own agent code on Foundry's managed compute with your choice of framework and orchestration; editable Bicep or Terraform can be ejected for customization
Builder's takeReviewing agent configuration alongside code is worth copying on any platform: a prompt or tool-list change should go through a PR like any code change. We are not on Azure, but I would move PandaClaws' agent prompts and tool permissions out of the admin database and into config files in the repo.
// Background · from #AI agents
Full timeline →- Nov 8 @GitHub in Slack and Teams is generally available: investigate bugs, create issues, implement changes and open pull requests from a conversation, with Canvas in Teams for reviewing plans together
- Nov 8 OpenAI introduces BioBasicsBench, a 100-task benchmark of how well AI agents interpret raw experimental data and handle everyday wet-lab science
- Nov 7 AWS runs Claude Code as a remote agent on Bedrock AgentCore: one microVM per task, up to three attempts, and a draft pull request unless verification passes