microsoft / microsoft/foundry-dev-tools

Show selected hosted-agent configuration in the workflow overview

Open
#605 1 comment 0 reactions 1 assignee View on GitHub

@qinezh is already working on this.

Since Jul 28, 2026.

canvas
Dominant language
JavaScript
Stars
2.1k
Forks
260
Avg merge
42m
Merged PRs (30d)
29

Description

Description

The build configuration rows do not expose what has been selected, so users cannot verify the agent’s model, toolboxes, skills, or guardrails from the workflow overview.

Each row should summarize its current state and support at least: loading, empty, configured, unavailable, and error. The design follow-up should define the compact summary; engineering should then connect it to authoritative configuration state.

Expected outcome

  • Model shows the selected deployment or an explicit empty state.
  • Toolboxes and skills show selected names or meaningful counts.
  • Guardrails show enabled, disabled, unavailable, or error state.
  • Loading and failure states do not look like valid empty configuration.
  • The summary remains visible when the configuration section is collapsed.

Evidence — C63

Build configuration without visible selected model, toolboxes, skills, or guardrails

Problem: Unable to know what's the inside of this config

Suggestion: Better to show what are the selected models, toolboxes, skills and guardrails.

Relationship

Parent: https://github.com/microsoft/foundry-toolkit/issues/602

Priority

P2 — Missing configuration transparency increases uncertainty and review errors but does not independently block creation.

Size

M — Requires compact-state design plus integration with model, toolbox, skill, and guardrail state.

Source

Internal UX audit, July 27, 2026. FigJam evidence. POC report: vscode/extension/ai-mlstudio/docs/experience-audit/agent-canvas-2026-07/report.md (not yet published upstream).

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.