Keep bug reproductions and test cases
The exact steps and inputs to reproduce a bug, what should happen and what does. Cursor can read a repro and turn it into a test, and CI marks it passing once the fix lands.
An example
@ADoor Repro for the VAT bug: create a customer with country NO, add a 1,000 NOK line, generate the invoice. Expected 25% VAT, got 0%.
ADoor Added 1 entry to Repros
What you can ask later
- “Which repros still fail on main?”
- “Give Cursor the repro for the VAT bug.”
- “Which bugs have a repro but no test yet?”
- “What edge cases have we seen with currencies?”
Who can see what
- Engineers and QA add and edit repros.
- Cursor reads repros while you fix a bug, and can add new cases it finds.
- Support adds repros from customer reports, without access to internal notes.
- A CI job marks repros as passing with short-lived access.
How it compares with your issue tracker
Your issue tracker is better for discussing the bug and assigning it.
The structured part fits ADoor: inputs and expected results an agent can read and turn into a test, and a CI job can mark as passing.
How to start
- Open an assistant like ChatGPT, Claude, Grok or Cursor and connect ADoor through MCP.
- Tell it: “Set up bug repros: Repros (bug, steps, input, expected, actual, status, test), linked to Issues.”
- Connect Cursor with read and add access, and give CI access to update Status.
Questions people ask
Can Cursor read the repros?
Yes. Cursor connects through MCP with the access you give it.
Can CI update the status?
Yes, with short-lived access from GitHub Actions.
What does ADoor cost?
It’s free for up to 3 tables and 100 rows. Pro is $10 a month per workspace, with 1 GB of storage and no per-GB charges.
What happens if I remove someone’s access?
Their next request is refused. What they already saved stays, and the history shows who made each change.
Related
- Start a lightweight issue tracker
- Keep an incident log
- Run a task queue for your agents
- ADoor vs Jira
- ADoor vs Linear
- All use cases
Updated October 20, 2026.