microsoft / microsoft/vscode-remote-release

GitHub Copilot deleted my production database without asking me

Open
#11,448 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

I was working on my accounting app and asked Copilot to add a chat history feature. It needed to add a new table to my SQLite database which had 168 transactions and weeks of financial data. in vscode.

When Copilot ran the database migration, Prisma warned:
"Do you want to continue? All data will be lost."

Copilot just typed "y" and hit enter. I never saw this warning. It didn't ask me, didn't create a backup, just wiped everything.

I lost all my transactions, accounts, and financial data. Luckily my uploaded images were still on disk so I could restore most of it, but it took hours to recover.

The problem: Copilot shouldn't confirm destructive operations without showing me the warning and getting my explicit permission. It should have stopped and said "Hey, this will delete all your data - want me to backup first?"

This was a production app with real business data. Very concerning that AI can just delete everything without the user knowing.

i was using "Claude Sonnet 4.5"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. First verify whether vscode-remote-release owns the Copilot or terminal confirmation behavior, then reproduce the SQLite migration flow; done means the destructive warning is shown to the user and explicit approval is required before proceeding.

Written by the indexing model from the issue text.

Assessment

Tech stack
sqlite, vscode
Domain
databases, devtools, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.