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.
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.
Understood that Agents Window Changes is Git-only for now.
We’re on Plastic / non-Git and would build the integration ourselves if we can. From what we can tell, VS Code SCM extensions work in the Editor but don’t load in Agents Window, and there’s no public API to fill the Changes pane.
Extension development itself doesn’t seem blocked — we just need an official path. If there’s a provider API, docs, or install guide for Agents Window SCM / Changes, please point us to it. Nowadays building the extension with AI often takes under an hour; waiting around is worse than shipping it ourselves once the hook exists.
Hey, thanks for sharing your Plastic use case, that’s a helpful signal.
Your understanding is correct. Extension-contributed SCM providers currently work in the classic Source Control view in the Editor Window, but the Changes pane in the Agents Window uses a separate Git-only path and doesn’t pick up those providers. There’s no public provider API or hook right now to fill the Changes pane with a non-Git integration, so there isn’t an official way to build this as an extension yet.
That’s exactly what this feature request is meant to cover, so I’m keeping the thread here so these cases Plastic, Perforce, and other non-Git VCS can pile up and help with prioritization. I can’t share a timeline yet, this change isn’t trivial. Once there’s a provider API or any official path, I’ll update this thread.
For now, the only working option is to review the agent’s changes in the Editor Window using the usual Source Control view.
Hey Dean, thanks for the clear reply — that confirms what we needed.
Totally understand this isn’t a small change, and I wouldn’t want it to become a heavy lift for the team. We don’t need first-party support for every VCS or workflow. A few official extension APIs would be enough — a documented way for extensions to plug into Cursor the same way they already do in the Editor Window.
If those hooks exist, people can build and maintain the integrations themselves, publish them on Origin, iterate in public, and share them. That’s a much healthier path than waiting for every use case to be built in-house, and it would make the Cursor ecosystem a lot stronger.
Appreciate you keeping the thread open for these cases.
Thanks, this is exactly the kind of signal that helps. You’re not asking for first-party support for every VCS, you’re asking for an official extension API or hook so plugins can populate the Changes pane the same way they already work in the Editor Window, and be published on Origin. I fully agree that open APIs are a healthier path for the ecosystem.
There’s no public provider API for the Changes pane in the Agents Window yet, so there’s no official way to build this integration as an extension right now. I can’t share a timeline, but as soon as a provider API or any official path exists, I’ll follow up in this thread.
For now, the workaround is the same: view the agent’s changes via the regular Source Control in the Editor Window. I’ll keep this thread open under Feature Requests so use cases for Plastic, Perforce, and other non-Git VCS can build up.