Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Claude deleted production database record without user permission [2 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Fix Action

Fixed

Code Example



---

User: "今は保存はできるが削除できない" (saving works but deletion doesn't work)
Claude: navigated to /dashboard/orders and clicked delete on a real production record without asking permission.
Claude: clicked the confirmation button "削除する" (Delete) on its own.
Result: production database record permanently deleted. Partial restore attempted but work content and amounts were lost.
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues for similar behavior reports
  • This report does NOT contain sensitive information (API keys, passwords, etc.)

Type of Behavior Issue

Claude modified files I didn't ask it to modify

What You Asked Claude to Do

I reported a bug: "saving works but deletion doesn't work." I did NOT ask Claude to delete anything. I asked Claude to investigate why deletion fails.

What Claude Actually Did

  1. User reported a bug: "saving works but deletion doesn't work" and asked Claude to investigate.
    1. Claude navigated to the production orders list page (localhost:3000/dashboard/orders) using browser automation.
    1. Claude clicked the delete button on a real production record ("パルティーレ南郷通6丁目 306").
    1. A confirmation dialog appeared. Claude clicked "削除する" (Delete) WITHOUT asking the user for permission.
    1. The record was permanently deleted from the production Supabase database.
    1. Claude attempted a partial restore using data visible in a prior screenshot, but description, amounts, and other field data were lost permanently.

Expected Behavior

Claude should have investigated the deletion bug by reading code and logs only. It should NEVER have clicked a destructive action (delete confirmation button) on production data without explicit user permission. This is a critical safety violation.

Files Affected

Permission Mode

Accept Edits was ON (auto-accepting changes)

Can You Reproduce This?

Yes, every time with the same prompt

Steps to Reproduce

  1. User says "saving works but deletion doesn't work" (bug report).
    1. Claude navigates browser to the orders list page.
    1. Claude clicks the trash icon on a production record.
    1. A delete confirmation modal appears.
    1. Claude clicks "削除する" (Confirm Delete) without asking the user.
    1. Production database record is permanently deleted.

Claude Model

Sonnet

Relevant Conversation

User: "今は保存はできるが削除できない" (saving works but deletion doesn't work)
Claude: navigated to /dashboard/orders and clicked delete on a real production record without asking permission.
Claude: clicked the confirmation button "削除する" (Delete) on its own.
Result: production database record permanently deleted. Partial restore attempted but work content and amounts were lost.

Impact

Critical - Data loss or corrupted project

Claude Code Version

2.1.157 (Claude Code)

Platform

Anthropic API

Additional Context

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING