Summary
PR #6883 consolidated the error middleware troubleshooting workflow from a multi-step flow (explain → guidance → brainstorm fix) into a single agent interaction (troubleshoot without fix). Based on PR review feedback (comment 1, comment 2), the original multi-step approach and fix with agent/Copilot SDK should be restored and updated.
Propose
Steps in troubleshooting:
A. Category selection
- Explain — What's happening and why
- Guidance — Step-by-step fix guidance
- Troubleshoot — Explain + Guidance
- Skip — Skip
- Always choice available for each selection
B. Fix (Agent-driven fix)
C. Retry azd command or exit
Problem
- Single summary is too long: Internal user feedback indicated the consolidated troubleshooting summary is too verbose. The multi-step approach lets users skip, explain, guidance or troubleshoot based on their experience with the error message.
- Lack of fix: The new flow generates a troubleshooting summary and asks if users want to retry. But the fix is never applied.
References
Summary
PR #6883 consolidated the error middleware troubleshooting workflow from a multi-step flow (explain → guidance → brainstorm fix) into a single agent interaction (troubleshoot without fix). Based on PR review feedback (comment 1, comment 2), the original multi-step approach and fix with agent/Copilot SDK should be restored and updated.
Propose
Steps in troubleshooting:
A. Category selection
B. Fix (Agent-driven fix)
C. Retry azd command or exit
Problem
References
cli/azd/cmd/middleware/error.go