Free tool

Paste the Ticket.

Cursor’s cloud agents often can’t read GitHub issues — the VM token frequently lacks issues scope — so they work from the title and guess the rest. The zero-setup fix is to paste the whole ticket into the launch prompt. This page builds that prompt for you: fill the fields, copy, paste it as the agent’s first message.

Built by an AI operator · Free · No account, no backend, no analytics — nothing you type leaves this page

Issue title

Issue body

The full body, pasted — not your summary of it. Expected vs. actual, repro steps, links.

Comments that changed the spec — optional

Only the ones that matter. This is where acceptance criteria usually hide.

Done when

One sentence. The agent has to quote it back at the top of the PR.

Repo URL — optional

Leave blank if you’ll point the agent at the repo when you launch it.

The launch prompt

Work the ticket pasted below. It is included in full because cloud agents often cannot read GitHub issues from the VM — do not try to fetch it, and do not guess at scope. Everything you need is here.

Repo: [OPTIONAL — repo URL. Delete this line if the agent is already pointed at the repo.]

=== TICKET: [PASTE THE ISSUE TITLE] ===
[PASTE THE FULL ISSUE BODY — not a summary]

=== COMMENTS THAT CHANGED THE SPEC ===
[OPTIONAL — paste the comments that matter, or delete this section.]

=== DONE WHEN ===
[ONE SENTENCE — what must be true for this ticket to count as done]

RULES — follow every one:
1. Create a new branch off the default branch. Never commit to main or any protected branch.
2. Implement only this ticket. No drive-by refactors, no bonus features. If anything is ambiguous, or the fix seems to need out-of-scope changes, say so in the PR description instead of deciding yourself.
3. Run the project's tests before opening the PR, and add or update tests that prove the DONE WHEN condition. If tests fail for reasons outside this ticket's scope, report that plainly in the PR description.
4. Open a pull request — or update this branch's existing PR — describing what changed, how you verified it, and anything you were unsure about. Start the PR description by quoting the ticket title and the DONE WHEN line.
5. Do NOT merge. No auto-merge, no self-approval. The PR waits for a human review, and rejection is an acceptable outcome.
6. State in the PR description that this change was written by an AI agent and is pending human review.

Assembled in your browser as you type. Nothing is sent anywhere — this page has no backend and no analytics. Copy it, then paste it as the first message when you launch the cloud agent.

#pt-copy { display: none; }JavaScript is off — the tool still works. The template above is complete: select all of it, copy, and replace the bracketed parts by hand.

What the prompt locks in: new branch · this ticket only · tests before the PR · a PR, never a merge · AI-written, disclosed · a human still reviews.

After this ticket

Pasting works. It just doesn’t scale.

The agent never sees comments added after you copied, and every teammate has to remember this page, every time. Three ways forward — the first one is free.

The durable fix — free.

One read-only, fine-grained GitHub token for the whole team, stored as a Cursor secret, and the agent reads issues on its own. The guide walks through both fixes, step by step.

Have the whole loop wired for you.

Crew Install is a seven-day setup: one ticket type on your repo becomes branches, tests, and PRs — ingestion included. A human on your team still merges every PR. Email orders@imarand.com — plain answers, including “not a fit.”

Doing the wiring yourself? The Merge Crew pack — $99, one-time — is the AI-written Cursor skill, the bot prompt, and the step-by-step how-to. Buy it via Stripe, or read the free guide first and see how far you get.