Fixing bugs
SuperDevAI fixes a bug the way a careful engineer does: find the cause, show the bug with a test, prove the fix, then change your code.
1. Describe the symptom
Say what you did, what you expected and what happened. Name the screen, page or endpoint if you know it.
Orders due today show as overdue on the dashboard after 6 pm.
Describe the symptom, not your guess at the cause. The agent checks the code either way, but a symptom gives it something to reproduce.
2. What happens next
- Investigation. It reads the relevant code, follows the data and names the cause, with the file and line.
- A failing test. It writes a test that reproduces your bug and runs it. The test must fail, for the right reason, before any fix is made.
- The fix, proven in a copy. It applies the fix to a copy of your project and runs the test there. Your files aren't touched until the fix passes.
- Apply. The proven change is shown to you for approval (in Dev mode) and written to your project.
- Check. It runs the tests again and reports what passed.
If a fix doesn't pass its test, it isn't written to your project. You're told what was tried and why it didn't work.
When the project can't run tests
Some projects have no tests, or tests that can't run on your machine yet (for example, packages not installed). The agent says so and offers choices: set up or repair the tests, or apply the fix without a failing test if you're comfortable with that. It never quietly gives up.
Partial fixes
On harder bugs a fix can be partial: it solves the scenario you described but misses a neighbouring case. After a fix, try the related cases too. If one still fails, tell the agent in the same conversation; it keeps what it learned. Please also report it, because partial fixes are what we're working on most.
Just explain, don't change
Add "Don't change anything" to get an explanation of the cause with no edits. For a broader look, ask "Review this project for bugs and security problems". The review lists findings and offers fixes, and only applies the ones you choose.
How long it takes
A typical fix takes 5–15 minutes, sometimes up to 30, because reading, testing and proving take time. The chat shows every step while it works.