Skip to content

feat: improve the hosted agent getting started with coding#2610

Merged
anchenyi merged 38 commits into
microsoft:mainfrom
anchenyi:improve-getting-started
Jun 15, 2026
Merged

feat: improve the hosted agent getting started with coding#2610
anchenyi merged 38 commits into
microsoft:mainfrom
anchenyi:improve-getting-started

Conversation

@anchenyi

@anchenyi anchenyi commented Jun 9, 2026

Copy link
Copy Markdown
Collaborator

Description

Continue development based on #2486 and #2435

Checklist

  • Tests pass locally (cd tests && npm test)
  • Title has one of the prefixes: fix:, feat:, feature:, chore:, misc:, test:, eval:
  • If modifying skill descriptions: verified routing correctness with integration tests (In tests/, npm run test:integration -- <skill> or npm run test:vally -- --skill <skill>)

Related Issues

zhenjiao-ms and others added 11 commits June 2, 2026 16:23
…eploy workflows

- Streamline create-hosted.md and deploy.md with clearer step-by-step flows
- Add reference docs for azd-ai-cli, local-run, and tools
- Add environment verification scripts (PowerShell and Bash)
- Update direct-code-deployment reference with consistent CPU/memory defaults
- Update SKILL.md description for better routing

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The previous defaults of 0.5 CPU / 1Gi often cause session_not_ready
timeouts during cold start. Update all prose and JSON examples to use
1 CPU / 2Gi as the recommended default.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* fix: restore eval

* fix: comment

* fix: use azd eval
Copilot AI review requested due to automatic review settings June 9, 2026 09:22

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR continues the microsoft-foundry skill refactor to make the “hosted agent getting started” flow primarily azd-first (scaffold → local run → deploy → invoke), while removing older/deprecated direct-code REST guidance and adding helper scripts/reference docs to reduce setup friction.

Changes:

  • Updates the microsoft-foundry top-level routing description and sub-skill summaries to emphasize azd-based hosted-agent workflows.
  • Rewrites the hosted-agent create and deploy docs around azd ai agent init/run/deploy/invoke, and adds new reference docs (azd CLI mental model, local run, tools/toolboxes).
  • Adds environment verification + project-id resolution helper scripts (bash/PowerShell) and removes the old direct-code deployment reference.

Reviewed changes

Copilot reviewed 13 out of 14 changed files in this pull request and generated 7 comments.

Show a summary per file
File Description
plugin/skills/microsoft-foundry/SKILL.md Updates skill description and sub-skill “when to use” blurbs to reflect azd-centric hosted-agent lifecycle.
plugin/skills/microsoft-foundry/project/create/create-foundry-project.md Adds auto-generated project naming guidance during project creation flow.
plugin/skills/microsoft-foundry/foundry-agent/invoke/invoke.md Adds an azd-first “fast smoke test” path and expands troubleshooting entries for azd invoke.
plugin/skills/microsoft-foundry/foundry-agent/deploy/references/direct-code-deployment.md Removes deprecated direct-code REST deployment reference.
plugin/skills/microsoft-foundry/foundry-agent/deploy/deploy.md Major rewrite of deploy workflow to focus on azd provision/deploy and async eval init.
plugin/skills/microsoft-foundry/foundry-agent/create/scripts/verify-environment.sh Adds a bash script to validate azd + extensions + auth + basic project/agent status.
plugin/skills/microsoft-foundry/foundry-agent/create/scripts/verify-environment.ps1 Adds a PowerShell equivalent environment verification script.
plugin/skills/microsoft-foundry/foundry-agent/create/scripts/resolve-project-id.sh Adds a bash helper to resolve Foundry project ARM ID from a project endpoint via Azure CLI.
plugin/skills/microsoft-foundry/foundry-agent/create/scripts/resolve-project-id.ps1 Adds a PowerShell helper to resolve Foundry project ARM ID from a project endpoint via Azure CLI.
plugin/skills/microsoft-foundry/foundry-agent/create/references/tools.md Adds toolbox/connection recipes and MCP wiring guidance for hosted agents.
plugin/skills/microsoft-foundry/foundry-agent/create/references/local-run.md Adds detailed guidance for running hosted agents locally with azd ai agent run.
plugin/skills/microsoft-foundry/foundry-agent/create/references/azd-ai-cli.md Adds an “azd ai CLI” mental model doc describing file roles and command surface.
plugin/skills/microsoft-foundry/foundry-agent/create/create-hosted.md Rewrites hosted-agent creation workflow around azd samples + brownfield init + local iteration.
.gitignore Ignores tmp/ at repo root.

Comment thread plugin/skills/microsoft-foundry/foundry-agent/deploy/deploy.md Outdated
anchenyi and others added 3 commits June 10, 2026 15:43
@XOEEst

XOEEst commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Looks good. Can you provide a conversation history to show the no-wait experience of eval init? E.g. will it prompt for check status after deploy completes?

And the change of eval init -> eval generate has been released in latest azd extension:
azd ext install azure.ai.agents --version 0.1.39-preview

@swatDong

Copy link
Copy Markdown
Contributor

Looks good. Can you provide a conversation history to show the no-wait experience of eval init? E.g. will it prompt for check status after deploy completes?

And also please wait for eval init -> eval generate to save future migration efforts. :)

Per test, agent auto-asks for user selection on eval:
image

Then call eval init --no-wait to trigger the generation:
image

And finally in summary mentioned eval suite generation in progress and eval run as next step:
image

fix: improve parallel install and local run stability
@XOEEst

XOEEst commented Jun 13, 2026

Copy link
Copy Markdown
Collaborator

Looks good. Can you provide a conversation history to show the no-wait experience of eval init? E.g. will it prompt for check status after deploy completes?
And also please wait for eval init -> eval generate to save future migration efforts. :)

Per test, agent auto-asks for user selection on eval: image

Then call eval init --no-wait to trigger the generation: image

And finally in summary mentioned eval suite generation in progress and eval run as next step: image

In the last snapshot, will eval run wait for eval suite generation to complete? I guess not, so shall we add a next step to wait for eval suite generation to finish?

@swatDong

Copy link
Copy Markdown
Contributor

Looks good. Can you provide a conversation history to show the no-wait experience of eval init? E.g. will it prompt for check status after deploy completes?
And also please wait for eval init -> eval generate to save future migration efforts. :)

Per test, agent auto-asks for user selection on eval: image
Then call eval init --no-wait to trigger the generation: image
And finally in summary mentioned eval suite generation in progress and eval run as next step: image

In the last snapshot, will eval run wait for eval suite generation to complete? I guess not, so shall we add a next step to wait for eval suite generation to finish?

Tried eval generate --no-wait and eval run, eval run does wait for eval suite generation to complete, so IMO the current eval run next step is enough.
image

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 38 out of 39 changed files in this pull request and generated 3 comments.

Comment thread plugin/skills/microsoft-foundry/foundry-agent/invoke/invoke.md
@anchenyi anchenyi changed the title [WIP] feat: improve the hosted agent getting started with coding feat: improve the hosted agent getting started with coding Jun 15, 2026
@anchenyi anchenyi merged commit 5812e44 into microsoft:main Jun 15, 2026
11 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants