Fast Path Pipeline: Path selection UI + wizard routing
Maintainers usually reply within 2 days
Nobody has claimed this yet.
- #566 by @gambtho — closed without merging
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 62/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- developer-experience, frontend
Research direction
Start with PathSelectionStep.tsx and WizardShell.tsx, then trace the wizard's repo readiness check and fast path orchestration hook. Implement the three documented choices, show the fast path when Dockerfiles are detected, and route each choice to the specified orchestration path with the stated time estimates.
Written by the indexing model from the issue text.
Description
Part of #557
Problem
Users need a way to choose between the fast path and the agent path. When a Dockerfile is detected, we should present the fast path as the recommended default, with clear time estimates so users can make an informed choice.
Changes
PathSelectionStep.tsx— the decision point UI showing three options:- "Deploy now" (recommended, ~3-5 min) — deterministic templates, no AI wait
- "Deploy now + AI suggestions" (~3-5 min + async PR) — fast deploy plus Copilot improvement PR later
- "Full AI generation" (~15-40 min) — existing agent path
WizardShell.tsxmodifications — add routing logic: after repo readiness check, if Dockerfiles found, show PathSelectionStep. User's choice routes to either fast path or agent path orchestration.- Wire up the fast path orchestration hook to the wizard when the user picks a fast path option
- Dominant language
- TypeScript
- Stars
- 115
- Forks
- 29
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/aks-desktop
-
[BUG] Misaligned Resource Name Field in AKS DesktopPossibly taken @vyncent-t claimed this 7 days ago. Openbug triage
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Azure/aks-desktop#1004 · 1 reaction · 1 assignee ·
Maintainers usually reply within 2 days
-
[FEATURE] Change cluster action label from “Delete” to “Remove”Possibly taken @tejhan claimed this 13 days ago. Openenhancement triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Azure/aks-desktop#992 · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Azure/aks-desktop#675 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/aks-desktop#674 ·
Maintainers usually reply within 2 days
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Azure/aks-desktop#458 · 1 comment ·
Maintainers usually reply within 2 days
All issues in Azure/aks-desktop
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
outline/outline#14348 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
[Bug]: Agent import retains quotes in .env API keys followed by inline commentsPossibly taken @yxr-2025 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
elie222/rakazo#2322 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
awslabs/visual-asset-management-system#804 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dsh-market/dsh-market#1027 · 1 comment ·
Maintainers usually reply within 1 day