Preconfigured Workflow for non-coders

Ideas Feature Requests
, ,
1

Feature request for product/service

Cursor IDE

Describe the request

Hi Cursor team :waving_hand:

Short version

Make it easier for designers and other non-coders to create pull requests with the correct Git workflow when using the visual editor.

Long version

I was really excited when the visual editor got launched because I realized this could allow me to introduce non-coders to Cursor and let them make their own visual changes. That’s incredibly powerful.

Ideally, these changes would be submitted as pull requests so I can review them, make adjustments if needed, and then merge them. However, following a proper Git workflow is quite difficult for non-coders, and the current UI is understandably optimized for developers (which is great!).

As a result, I currently need to walk designers through a fairly complex process.

My current tutorial for designers

  1. Check out the develop branch
  2. Make your changes
  3. Click Review and ignore all the code that appears
  4. Click Commit
  5. Wait for the commit message to appear (optionally edit it)
  6. Click Commit and Create PR
  7. Click on Open from new branch
  8. Wait for the browser to open, and create the PR in the browser
  9. Make sure to switch back to the develop branch before starting the next change

This works, but it’s far from intuitive for someone who doesn’t work with Git regularly.

Proposal

Minimal solution

  • Add a configuration option where users can indicate whether they understand code or not.
  • For users who don’t, surface a “Create PR” button directly in the chat or visual editor.
  • Allow teams to define rules for how the Git workflow should be handled, so Cursor can automatically create PRs in the correct way.

Better solution (based on my mockup): Abstract away Git entirely

Introduce a Designer Mode (next to Agents and Editor in the top left):

  • Designer Dashboard: Show a list of the user’s current PRs and their status
  • Allow clicking a PR/feature to either:
    • Open it on GitHub, or
    • Check out the corresponding feature branch to continue working on it
  • Add an “Add new feature” button that:
    • Opens the chat with the visual editor/browser side by side
  • After finishing a feature, the user clicks “Publish feature”, which creates and opens the PR on GitHub (with the correct git workflow)

This would let non-coders focus on design and intent, while Cursor handles the Git mechanics behind the scenes.

I’d also love to hear how other teams handle this today. Any workarounds or best practices are very welcome.

Thanks for building such an exciting product!

Screenshot / Screen Recording

cursor-design-mode-fr.png
cursor-design-mode-fr.png1222×2277 184 KB

Operating System (if it applies)

Windows 10/11
MacOS
Linux