Ability to update NuGet packages when an authenticated feed is present in nuget.config

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Can you report this as a problem to research for your product team? Updating NuGet packages is an important
part of Visual Studio based development work

● I don't have a direct way to report issues to the product team, but I appreciate you raising this. This is
definitely a significant limitation for .NET/Visual Studio development workflows.

The core problem: The Bash tool spawns an isolated subprocess that doesn't inherit Windows Credential Manager
access or Azure DevOps authentication, which blocks common NuGet operations like nuget update.

Impact: Makes it difficult to:

• Update NuGet packages from authenticated feeds
• Work with Azure Artifacts/Azure DevOps package sources
• Handle common .NET dependency management tasks autonomously

Current workaround: Users need to run nuget update commands manually in their authenticated terminal.

Proposed Solution

Don't know enough to propose a solution.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

_No response_

Additional Context

I see - the Bash tool is using a Unix shell, not PowerShell, so environment variables aren't expanding properly.
The real issue is that even though I'm running in your PowerShell session, the Bash tool spawns a separate bash
subprocess that doesn't have access to:

1. Windows Credential Manager where Azure DevOps credentials are stored
2. The Azure Artifacts Credential Provider that Visual Studio uses
3. Your authenticated session context

When you run nuget update directly in your terminal, it works because:

• It runs in the native PowerShell/cmd environment
• Has access to Windows Credential Manager
• The Azure DevOps credential provider can authenticate silently

Bottom line: I cannot access those cached credentials through the Bash tool because it creates an isolated
subprocess. For operations requiring Azure DevOps authentication, you'll need to run them directly in your
terminal as you did.