Support extension-contributed SCM providers in the Agents Window

Ideas Feature Requests
, , ,
1

Feature request for product/service

3rd Party Extensions

Describe the request

In the classic Editor Window, source control works through VS Code-compatible SCM extensions. This allows non-Git version control systems to show changed files, diffs, branches/status, and related actions in the Source Control view.

In the Agents Window, the Source Control / Changes pane appears to only detect Git repositories. For workspaces managed by another VCS through a VS Code SCM provider, the pane shows “Use a Git repository to track changes” / “Initialize Repository”, even though the same workspace shows changes correctly in the Editor Window.

Expected behavior:
The Agents Window should either reuse the same extension-contributed SCM providers as the Editor Window, or expose an equivalent provider API so non-Git SCM integrations can populate the Changes pane.

Why this matters:
Without this, users on non-Git repositories cannot reliably monitor agent changes, review diffs, accept/revert changes, or use checkpoint/change-management workflows from the Agents Window. The workaround is to keep switching back to the Editor Window, which breaks the Agents Window workflow.
Suggested scope:

  • Load and display VS Code SCM providers in the Agents Window Changes pane.
  • Avoid showing “Initialize Repository” when another SCM provider is active for the workspace.
  • Support basic changed-file and diff viewing for non-Git SCM providers.

Operating System (if it applies)

MacOS

5

Hey, thanks for the detailed feature request, it’s really well written.

You’re right. The Changes pane in the Agents Window currently only works with Git, while the classic Source Control view in the Editor Window also picks up extension-contributed SCM providers. This is a current limitation of the Agents Window, not a bug, which is why you see Initialize Repository for non-Git workspaces.

The request makes sense, I’ve logged it as a feature request. There’s no timeline yet. It’s a non-trivial change, so I won’t promise dates. For now, the only workaround is the one you mentioned: review changes in the Editor Window.

I’ll keep this thread in Feature Requests so other users on non-Git VCS can upvote it, that helps with prioritization. If there’s an update, I’ll reply here.