Consider moving the AZSDK CLI to use sampling
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 130
Description
Experimented here https://github.com/Azure/azure-sdk-tools/pull/15506 but didn't get very far, main benefit is that in the MCP case the token usage is way lower, the complexity of needing the have copilot.exe in the right spot is removed, and accuracy is generally better due to the context being the user's context. However, the mix of needing the SDK in the CLI case and sampling in the MCP case is a little annoying so wasn't sure if we wanted to pursue it.
Just wanted to throw this out for consideration in case someone else ever wants to try.
Contributor guide
Research direction
Start by reviewing PR #15506 and the CLI and MCP approaches described in this issue. Compare their token usage, copilot.exe dependency, context, and accuracy, then define a concrete decision and acceptance criteria for whether sampling should replace the CLI SDK path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ai, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100