A bug report that carries its own repro, plan and fix.
For QA engineers turning bugs into reproducible work
Keep the reproduction in the project and ask the agent for a plan. When you add a case mid-run, /also puts it on the plan without stopping the work, and every edit is a version you can restore.
What is in it
- Project context that holds the reproduction
- A plan before any tool work
- /also to add a case without stopping the run
- A version of every agent edit
- Saved git history brought back as it was
- Free for one profile
How the work gets done
Free Bandicot core
The free plan has every capability for one profile. Bring a provider key, a local model, or both; a provider's own bill stays yours.
A trusted harness around the model
Bandicot gives every agent a project, tools, a session that survives restarts, approvals, and a clear place to stop.
Projects that hold the work
Keep files, context, plans, and decisions with the project instead of losing them in a disposable chat.
Durable work sessions
Close the window, restart, or pick up from another of your Macs without turning the work into a brand-new conversation.
Try it with the door open
No contract. Cancel any time from your account and keep the plan until the end of the period you paid for.
Your files stay yours
The agent does its work in your own folders on your Mac, so the files are yours to keep.
Start without paying
The free plan has every capability for one profile, and asks for no card.
Put a run back
Every changed file is a version, so a run you regret is one click from undone.
Everything on one slip
Projects hold the context while Versions records file edits, and ignored logs and build output stay out of the history.
bandicot
- Asked
- Keep reproduction notes and agent changes tied to the same project
- Before it wrote
- It asked, and waited for your answer
- Files kept
- historyversion kept
- notes.mdversion kept
- projectversion kept
- Stands behind
- The /also command adds work to the plan without stopping the current work
- Versions follows .gitignore rules to leave out ignored build output, logs and caches
- You can bring saved git history back to the project
- Paid to Bandicot
- Free
- Model bill
- from your provider
Keep a bug's reproduction and proposed fix together.
The repro, the plan and the edits live in one project. Versions skips build output and logs, so the history shows only the work that matters.
Reproduction Desk
Every line below is already in the plan. Nothing here is an extra you pay for.
- Project context that holds the reproductionincluded
- A plan before any tool workincluded
- /also to add a case without stopping the runincluded
- A version of every agent editincluded
- Saved git history brought back as it wasincluded
- Free for one profileincluded
Free for one person on your Mac, no card. Your model provider bills you directly.
No contract. Cancel any time from your account and keep the plan until the end of the period you paid for.
Questions before you start
Does it certify that the bug is fixed?
No. Run and review your checks. The workspace records the agent's tool results and file changes, not a certification.
Can an agent change files without asking?
Writes, commands and spend outside your permissions file wait for approval. The model cannot grant itself permission.
Can I take back an agent's edits?
Yes. In projects you enrol in Versions, file changes are recorded. Restore a file or undo a whole run, with or without Git.
A bug report that carries its own repro, plan and fix.
Free for one person on your Mac, no card. Your model provider bills you directly.