Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

Define a shared Chat and canvas workflow for hosted-agent creation

Đang mở
  • Có gì không ổn?
#602 1 bình luận 0 reaction 1 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

@qinezh đang làm issue này rồi.

Từ ngày 28/7/2026.

Đánh giá

Issue này chưa được đánh giá.

Mô tả

canvas

Description

Copilot Chat and the Foundry agent canvas do not currently behave as two views of one hosted-agent workflow. Users may start from Chat or open the canvas directly, but intent, progress, deterministic choices, and deployment state are not shared coherently. The signed-out canvas also exposes later steps too early, while creation does not offer clear routes for samples or existing local agents.

This parent issue should establish the product and interaction contract before the system-level findings are decomposed into implementation work.

Decision required

  1. Define which surface owns intent, progress, confirmation, generated files, deployment state, and recovery at each step.
  2. Define the state shared bidirectionally between Chat and canvas.
  3. Use progressive disclosure based on authentication, project selection, task progress, and agent readiness.
  4. Decide the supported entry routes: start from intent, start from a sample, or continue an existing local hosted agent.
  5. Define when deployment becomes available and what “ready to deploy” means.

Record the review outcome as Adopt, Needs design, Defer, or No action. Create implementation work only for adopted routes and contracts.

Findings

C59 — Chat–canvas interoperability

Chat-first entry showing the Chat and canvas interoperability gap

When a prompt started from the chat, the agent cannot interchangeably operate with Foundry agent canvas.

I think some users would start from opening Foundry agent canvas manually and click through the buttons to create agents, but others would feel more comfortable to start from the chat.

The gap here is that the chat -> foundry agent canvas is not working well, the canvas must be operated deterministically on the canvas.

What I would expect to have as a smooth experience is, the canvas remains as a supporting role, showing the progress, illustrating clear steps, and operate deterministically when user needed it. Otherwise, it should interchangeable work between agent chat and canvas, e.g., if I open a word canvas, I can ask agent to edit the content in the word, and it does show the changes in real-time on the canvas side.

C60 — Progressive first-run workflow

Signed-out overview showing all workflow steps at once

Problem: All steps are linearly displayed, although the very first step might be signing in.
Problem: Deploy to Foundry seems to be highlighted but it should not be the primary action in the beginning.

Can we perhaps show the UI according to the step? For example, for first-timers, we show sign in exp, and ask them to either create a new hosted agent or pick up from existing ones..

C61 — Creation and continuation routes

Creation choices without samples or existing hosted agents

Problem: No option to select existing hosted agent

Problem: No samples

Source reply:

Suggestion: Show three options; start with intent, provide samples, pick up from the existing hosted agents (local)

Follow-up work items

  • C62: Keep the workflow focused on the active step.
  • C63: Show selected hosted-agent configuration.
  • C64: Gate deployment until prerequisites are complete.

Size

L — Cross-surface product, interaction, and state-contract decision.

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).

Ngôn ngữ chính
JavaScript
Star
2.1k
Fork
262
Merge trung bình
1 ngày 3 giờ
Pull request đã merge (30 ngày)
29

Chuẩn bị môi trường

Dự án này không cung cấp dev container, Dockerfile hay hướng dẫn đóng góp, nên bạn cần tự thiết lập môi trường: hãy bắt đầu từ README và xem hướng dẫn đóng góp lần đầu của chúng tôi để biết các bước chung.

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của microsoft/foundry-dev-tools

Tất cả issue của microsoft/foundry-dev-tools

Issue tương tự

Thêm issue về JavaScript

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.