Approvals and safety
You decide what changes. Here's what SuperDevAI asks before doing, what it never does without you, and how to undo.
Approval cards
In Dev mode each change to a file and each command shows an approval card first, with the exact change and its +/− line counts.
- Approve: do this one.
- Approve for this session: don't ask again for this kind of action until the session ends.
- Deny: and say why if you like. The agent responds and adjusts instead of stopping.
Edits to a test file the agent created in the same run are approved automatically, so a bug fix usually shows one or two cards.
Always asked, in every mode
Even when SuperDevAI works on its own (Simple mode, or --yes on the command line), it always stops and asks a person before it:
- publishes an app,
- pushes to Git,
- deletes anything outside your project folder.
If nobody is there to answer, those actions don't happen.
Undoing changes
- Use Git. Commit before you ask for a change, so you can always go back.
- A bug fix is proven in a copy of your project first; a fix that fails its test is never written.
- On the command line,
superdevai rollback <task-id>puts files back the way they were before a task.
Your code and your keys
- To do its work, the agent sends the parts of your code it needs to the AI model provider. With managed credits that goes through SuperDevAI's service; with your own key it goes to your provider.
- Your own model keys are stored in the Windows credential store on your computer, not on SuperDevAI's servers.
- Documents the agent writes never contain secrets: it names where a password or key lives instead of copying it.
- Problem reports never include your code, your prompts or the AI's answers, and keys and passwords are removed automatically. See Reporting a problem.
Your account
- SuperDevAI needs an approved, active account to run, so a copy of the app can't be used without one.
- After several wrong passwords in a row, sign-in for that email pauses for about 15 minutes.