Confirm destructive folder deletes in chat explorer
From the PR description
Summary
- route assistant chat explorer folder deletes through a confirmation popup
- show how many nested folders and documents will be permanently deleted
- remove deleted documents from local chat explorer state and close stale document tabs after deletion
Bug
The assistant chat project explorer called the recursive folder-delete endpoint immediately. That backend endpoint permanently deletes documents in the folder tree, but this view updated local state as if those documents were only moved out of the folder. A user could delete documents from the chat explorer without a destructive-action warning and keep seeing stale document entries until refresh.
Verification
- NEXT_PUBLIC_SUPABASE_URL=http://localhost:54321 NEXT_PUBLIC_SUPABASE_PUBLISHABLE_DEFAULT_KEY=dummy npm run build --prefix frontend
- npm run build --prefix backend
Note: running the frontend build without placeholder Supabase public env values still hits the existing supabaseUrl is required prerender failure fixed separately in #173.
Our analysis
Confirm and sync destructive folder deletes in the assistant chat explorer — read the full analysis →
Think the analysis missed something the PR description covers?
Commits in this PR (2)
| SHA | Subject | Author | Date | |
|---|---|---|---|---|
2b4eda30 | Confirm destructive folder deletes in chat explorer | Lawyered | 2026-06-10 | ↗ GitHub |
54993c21 | Merge remote-tracking branch 'origin/main' into fix/confirm-chat-folder-delete | willchen96 | 2026-08-04 | ↗ GitHub |
# Conflicts: # frontend/src/app/(pages)/projects/[id]/assistant/chat/[chatId]/page.tsx | ||||
Capture this PR into my fork
Download a Markdown prompt that tells Claude how to port every
commit in this PR into your working tree. Run it via
claude -p < capture-pull-174.md from
inside the repo you want the changes in.