Support Arcanist (arc diff) workflows beyond GitHub PRs

Feature request for product/service

Background Agent (GitHub, Slack, Linear,…)

Describe the request

Many engineering teams still use Arcanist / Phabricator-style review workflows instead of GitHub pull requests. It would be very valuable if Cursor could better support these workflows, rather than assuming GitHub PRs are the only review path.

Today, Cursor is excellent at code search, editing, and fix generation. However, in teams that use arc diff, the real delivery workflow usually includes more than just writing code:

  • finding the right code and context
  • making or updating the fix
  • running verification steps
  • submitting changes with arc diff
  • passing repository-specific quality gates or code admission checks
  • waiting for human review and final acceptance

Current gap:
Cursor helps a lot with coding itself, but teams using Arcanist still have to manually bridge the workflow after the code change is ready. This makes it harder to adopt Cursor in environments where arc diff is the standard review path.

What would help:

  • better support for Arcanist / arc diff workflows
  • the ability to assist with preparing and submitting diffs
  • workflow support that does not assume GitHub PRs are the only destination
  • better compatibility with enterprise or internal development platforms that use non-GitHub review systems

Ideal outcome:
Cursor should fit into real-world engineering workflows regardless of whether a team uses GitHub PRs or arc diff. Supporting Arcanist-based review flows would make Cursor much more practical for many enterprise teams and legacy but still important internal platforms.

Operating System (if it applies)

MacOS