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

Ideas Feature Requests
8

Hey, good call. Runbook instead of reopening the same problem on every project is exactly the gap that hurts the most.

Some of this can already be set up today, without waiting for a turnkey flow:

  • Skills SKILL.md You can write your deploy runbook once: push to deploy steps, required env vars, deploy targets, rollback path, and the agent will reuse it across projects. This is the repeatable checklist you mean. More details: Agent Skills | Cursor Docs
  • Project rules .cursor/rules For repo specific conventions like always deploy via wrangler with these flags so you do not have to explain it again. Rules | Cursor Docs

What is still missing as a single layer is a unified safe handoff around deploys: scoped and revocable access, audit logs, limits. That came up above. It is a votable direction, and there is a feature request here: Granular approval options for terminal commands and MCP tool calls It is worth upvoting and adding concrete details about runbook and rollback as requirements.

So first time OAuth is still manual for security reasons, but everything else is already pretty workable with Skills plus rules. Try it and let me know how much it covers your case. That will help clarify what is actually missing in the feature request.