Deployment and account setup should be automatable by the agent, not a multi-day manual workflow

Ideas Feature Requests
1

I’m building a real business site (676 pages, Stripe, PDFs) with Cursor. After three full days, the site still isn’t live. The product is strong at writing code, but the deployment workflow is brutal for non-developers.

I had to manually sign up for Cloudflare, authorize GitHub, create a repository, install GitHub Desktop because Git isn’t available in the terminal, delete and recreate the repository, publish, and then go back to Cloudflare — all steps were taken one click at a time with the agent.

For a “top-tier” dev tool, there’s no good reason the agent shouldn’t be able to connect to GitHub, Cloudflare, and Stripe (with my approval) and handle this tedious work. The current flow consumes days per project. I can’t spend 3–7 days on setup for every small project. That’s a subscription decision for me: if the tool can’t shorten end-to-end time to live, not just time to code, the cost becomes questionable because it’s not just money I’m spending.

4

Hey, thanks for the detailed feedback. Your request is clear: you want an agent that, with your approval, can connect to GitHub, Cloudflare, Stripe, and handle the whole deploy flow, instead of sending you through dozens of manual clicks. That makes sense. I’ll move this thread to Feature Requests so it reaches the right team and can collect votes. There are also a couple related deploy threads where you can add a vote or extra details: Deployments support in Cursor and Request for Cursor to Support Remotely Hosted Deployments.

For now, you can already cut down some of the steps:

  • Git in the terminal: Cursor uses your system git, it doesn’t ship its own. Install git on your machine on Windows, use Git for Windows. After a restart, git will be available in the terminal, and you won’t need GitHub Desktop.
  • Deploy via CLI with auto-run: the agent can run CLIs like wrangler for Cloudflare, gh for GitHub, and stripe right in the terminal. You log in once wrangler login, gh auth login, then the agent can do push and deploy for you if you enable terminal auto-run.
  • MCP servers: for connected services, the agent can operate them via MCP with your approval for each action: Model Context Protocol (MCP) | Cursor Docs

What still can’t be automated is the initial signup and first-time auth for new third-party accounts. That requires manual OAuth or login on your side for security reasons.

Let me know how it goes with git and the CLI, it should remove a good chunk of the routine.