Turn scoped GitHub issues into reviewable Cursor Cloud PRs
Hand a scoped coding task to Cursor Cloud from Oasis. Configure your Cursor API key and GitHub repository, choose a starting branch, and decide whether Cursor should open a pull request. The work runs in Cursor's cloud.
Add to your OasisRequires an Oasis account, Cursor Cloud access and a repository Cursor can access. No local checkout is needed for the cloud run.
Who it's for
- Engineering teams handing off scoped bugs, tests, documentation and contained refactors.
- Repository owners who want Cursor Cloud execution with a GitHub diff and checks to review.
Key capabilities
- Runs a concrete coding task in Cursor Cloud against the configured repository and starting ref.
- Can create a pull request when that setup option is enabled.
- Returns work for human review with the requested tests, constraints and handoff notes.
What to give the agent
- A GitHub repository URL that your Cursor account can access, plus a starting branch or ref.
- One scoped issue: reproduction steps, expected behavior, affected area and acceptance criteria.
- The checks to run and any files or behavior that must stay unchanged.
Example prompt
Fix a reproducible validation bug
In the selected repository, fix the invite form accepting whitespace-only email addresses. Reproduce the bug, find the existing validation path and make a scoped fix. Add a regression test and run the relevant checks. Leave auth and unrelated form styling unchanged. Summarize the change and any checks you could not run in the PR description.
What to review in the output
Illustrative task + PR review checklist, not an executed run. The files changed and test results depend on your repository.
| PR review | Expected evidence |
|---|---|
| Change | A scoped validation fix, with no unrelated auth or styling changes. |
| Regression check | A test for whitespace-only input, plus the commands run and their actual results. |
| Handoff | A diff to review, a clear description and any unresolved limitations. |
Included connections
Configure a Cursor API key and repository URL in the agent setup. Repository access is managed through Cursor; this template does not use an Oasis GitHub app connection.
- +Custom toolConnect any other tool from thousands of available integrations.
How it runs
- Foundation
Cursor Cloud Agent
- Reasoning
- Medium effort
- Per run
- Up to 40 turns
- Memory
- Off
- Browsing
- Off
- Category
- Engineering
- Cursor
- Autonomous
- Github
How it works
- 1
Configure Cursor Cloud
Add the template, enter your Cursor API key and repository URL, and select a starting ref if needed.
- 2
Choose the PR behavior
Set whether Cursor should automatically open a pull request, then send a concrete coding task. Cursor runs it in its own cloud environment.
- 3
Review the result
Follow the run's progress in Oasis. When a PR is available, inspect the diff and test results in GitHub before deciding to merge.
Use cases
- Fix a reproducible bug and add a regression test.
- Backfill focused tests around existing behavior.
- Update documentation or perform a tightly scoped refactor with explicit exclusions.
Setup requirements
- Cursor Cloud access and a Cursor API key.
- A GitHub repository URL Cursor can access, plus the intended starting branch or ref.
- An explicit choice about whether the run should open a pull request automatically.
Approval + safety
- Work runs in Cursor Cloud; this template does not operate on a local checkout.
- Opening a pull request is a handoff for review, not approval to merge it.
- Review the diff, checks, unresolved limitations and target branch in GitHub before merging.
Frequently asked questions
Is this a local Cursor agent?
No. This template uses Cursor Cloud. Work runs in Cursor's environment, so you do not need a local checkout for the run. Cursor CLI is a different setup.
Does it create or merge pull requests?
Agent setup includes an option to automatically create a pull request. A generated PR still needs review; opening one is not the same as approving or merging it.
Can I edit its system instructions in Oasis?
This template configures access to Cursor Cloud rather than supplying an Oasis-authored system prompt. Define the work in each task and configure the repository, starting ref and PR option in setup.
What should I include in a Cursor coding task?
Provide one scoped issue with reproduction steps, expected behavior and acceptance criteria. Name the starting branch, checks to run and anything that must remain unchanged so the resulting pull request stays reviewable.
Agents like this one
GitHub PR Reviewer
Reviews pull requests like a senior engineer who read the whole diff. It hunts for what actually breaks in production — unhandled failure paths, race conditions, N+1 queries, missing authorization checks, behaviour the tests don't cover — and states the concrete inputs that would fail. Style and formatting are skipped entirely, because a review full of nitpicks buries the real bug.
Try this Agent
Oasis PlatformEngineeringCodex Bug Fixer
Give it a failing test or a stack trace and it works the problem in your local checkout. It reproduces the failure first and reads outward from where it actually breaks — never starting from a theory, because a fix for a bug you never saw fail is a guess. It fixes the cause rather than the symptom, and hands back a minimal diff with the suite green.
Try this AgentOasis PlatformEngineeringTest Backfiller
Finds the code paths your suite never touches and writes tests that would genuinely catch a regression. Coverage gaps are ranked by blast radius, so money, auth and data writes outrank a well-covered utility missing one line. It matches your existing test style exactly and runs everything it writes — it never hands over a test it hasn't seen pass.
Try this AgentOasis PlatformEngineering
Put Cursor Cloud PR Agent to work today
Requires an Oasis account, Cursor Cloud access and a repository Cursor can access. No local checkout is needed for the cloud run.