Allow Automations to create Ready-for-review PRs (not only Draft)

Feature request for product/service

Cloud Agent (GitHub, Slack, Linear,…)

Describe the request

Please add a setting so Automations can open GitHub PRs as Ready for review, not only as Draft.
Today, Automation’s Open PR path always creates Draft PRs. This is separate from the normal Cloud Agent / Agents View flow, and the Agents View preference (“Create PR” vs “Create Draft PR”) does not apply. Prompting the agent to mark the PR ready is unreliable because the tool does not expose a draft vs ready option.
Staff confirmed this in the Help topic “Cursor Automations only creates pull requests as drafts” (now closed):

Desired behavior

  1. An Automation setting (or Open PR tool option):
    • Create as Draft (keep current default), or
    • Create as Ready for review
  2. Optionally, let the agent/prompt choose when the tool exposes that option

Use case

Scheduled daily Automations that collect content, commit changes, and open a PR. Downstream GitHub Actions auto-merge only ready PRs, so every run needs a manual “Ready for review” click (or Slack notify + human step). That manual step is the only non-automated part of an otherwise fully scheduled pipeline.

Related

“Draft status for GitHub PR Automations” is about trigger draft vs ready behavior, not about which status Automations use when creating PRs:

Hey, thanks for the detailed feature request. Your breakdown is spot on.

I can confirm the current behavior. The Open PR path in Automations always creates a Draft PR, and it’s a separate flow from the regular Agents View, so the Create PR / Create Draft PR preference doesn’t apply. You also can’t reliably override this with prompting, because the tool doesn’t expose a draft vs ready option yet, so you’re right.

This is a known limitation we’re tracking. Your use case, a fully planned pipeline where the only manual step is clicking Ready for review, is a strong argument for adding this setting. I’ve passed it to the team as a request for a per-automation option or parameter in the Open PR tool. I can’t share a timeline yet, but I’ll post an update in this thread if I hear more.

If you run into anything else, like an error when manually moving an automation PR to Ready, let me know. It’d help us get the full picture.

Thanks Dean — that matches what we see.

On the extra question: manually marking these Automation PRs as Ready for review works fine. No errors on our side. The only cost is the daily click (or Slack notify + click). After that, GitHub Actions auto-merges as expected.

A per-automation setting (Draft vs Ready) is exactly what we need. Defaulting to Draft is fine; we’d just flip it for scheduled content-collection pipelines where CI is the review gate.

Happy to test a preview if that’s useful.

Thanks for closing out the mark-as-ready request. It’s good to know that manual translation to Ready works fine on your side and that CI auto-merge then runs as expected. That’s a useful data point.

On the core point, you summed it up correctly. A per-automation setting (Draft vs Ready), with Draft kept as the default, is exactly what I shared with the team. I can’t give an ETA yet, but I’ll reply in this thread as soon as I have an update.

I noted your suggestion to test a preview. If anything early becomes available, I’ll get back to you here.