Use case
Clear a ticket backlog while your team keeps the final say
Short answer
Your developers write tickets with acceptance criteria. Reqursor Development implements them in your repository and, by default, opens a draft pull request for your team to review.
Who does what
Your developers write the tickets, including the acceptance criteria that define done. Reqursor Development implements each ticket in your repository, and your team reviews the result.
How the queue works
Write tickets in the built-in queue or import them from a connected tracker. A ticket cannot move to Ready without at least one acceptance criterion, and labels, priority and dependencies decide the order.
Run one ticket, run every Ready ticket, or switch on Autopilot for a project. Autopilot works within the working hours you set, skips a ticket whose dependency has not shipped, and runs one ticket per project at a time.
- Draft: still being written, not yet eligible to run
- Ready: has acceptance criteria and is waiting to be picked up
- Running: the pipeline is working the ticket
- Needs review: the evidence fell short, with a report of what was tried
What lands in your repository
With the default branch strategy each ticket ships on its own branch and opens a draft pull request, so two tickets in flight give two branches and two pull requests. A single shared working branch is the alternative.
The agent cannot force-push, rewrite history, skip your git hooks or push to a branch you protect. For a ticket imported from GitHub or GitLab, the result can be reported back to the original issue if write-back is switched on for that connection.
When a ticket needs a person
Tickets that need a decision collect in one needs review inbox. A ticket that falls short lands there with a report of what was tried. From there you can retry it with a hint, skip it, or edit it and send it back to Ready.
If a shipped ticket turns out to be wrong, Revert undoes it with a new commit, never a history rewrite.
What counts as falling short, and the checks and evidence behind a ship decision, are covered in Ship with evidence.
Good fit
- A backlog of well understood tickets that you can write as checkable acceptance criteria
- Teams that already review changes as pull requests
- Repositories with build, lint, typecheck or test commands the agent can be held to
Not the right fit
- Work that cannot be written as acceptance criteria, because a ticket cannot be Ready without at least one
- A repository with no build, lint, typecheck or test commands, because there are fewer checks to hold the agent to
- No Linux server you operate to install it on, because there is no hosted version of the product itself
- Status today: Onboarding founding customers
Frequently asked questions
Write each ticket with a title, a description and an acceptance criteria checklist, or import it from a connected tracker. A ticket cannot move to Ready without at least one criterion. Specific, checkable criteria give the reviewer and the verifier something to confirm.
Yes, within limits you set. Switch on Autopilot for a project and it works through Ready tickets in the order of their position and priority, once their dependencies have shipped. It only runs within the working hours you set, and it runs one ticket per project at a time.
By default each ticket ships on its own branch and opens a draft pull request. You can choose a single shared working branch instead. Either way the agent cannot push to a branch you protect, force-push or rewrite history.
The ticket lands in Needs review with a report of what was tried and why it stopped. You can retry it with a hint, skip it, or edit it and send it back to Ready for another run.
Related pages
Use case
Ship with evidence
Reqursor Development links every acceptance criterion to the lines of the diff that satisfy it, runs your own checks as hard gates, and has a second agent verify the change before a security scan and the ship decision.
Use case
Control AI spend
Every project has spending caps per ticket, per day and per calendar month. When a cap is hit, Autopilot starts nothing new, Run now is blocked and the message names the cap that stopped it.
Comparison
Versus editor AI assistants
An editor assistant works inside a developer’s session. Reqursor Development takes tickets from a queue, runs on a Linux server you operate and ships only through your checks and evidence.
See it on your own codebase
See Reqursor Development work through real tickets on a repository like yours, in a 30-minute call with the people who build it.