URGENT: Accidental project deletion by Codex CLI automation — recovery request (SU-422776)

[donghongfei]

Hello Supabase team and community,

I am urgently requesting help regarding an accidental project deletion that occurred today, July 16, 2026, only a short time before this post.

Private support ticket: SU-422776
Deleted project name: pulse
Region: Southeast Asia (Singapore)
Plan: Free

Exact sequence of events

1. I instructed OpenAI Codex to delete a different Supabase project named test, then create a new project named resume-fit.
2. Codex used the Supabase CLI to list my projects.
3. The project list correctly showed both pulse and test, with different project refs.
4. Codex incorrectly reversed the association between the project names and their refs.
5. Codex executed supabase projects delete [PULSE_PROJECT_REF] --yes, believing the ref belonged to test.
6. The CLI returned Deleted project: pulse.
7. Codex immediately recognized the mistake and stopped. It did not delete test, create resume-fit, apply migrations, or perform any other Supabase operation afterward.

The operation was performed with Supabase CLI 2.105.0. Codex was following the project-local Supabase Agent Skill v0.1.2. The skill itself did not provide the wrong project ref; the destructive error was Codex's incorrect project-name-to-ref mapping and failure to verify the project name immediately before deletion.

For privacy, I have included the full project ref and organization details in support ticket SU-422776, rather than posting them publicly here.

I understand the documentation says deleted projects cannot normally be recovered. Because the deletion was reported within minutes, I am asking whether a Supabase team member can urgently check for any remaining internal deletion queue, delayed cleanup process, infrastructure snapshot, or other recovery path.

If full recovery is impossible, is there any way to recover any remaining database, Auth, Storage, configuration, or backup data?

I searched existing discussions before posting, including Accidental project deletion — any recovery options?, but this case has an active support ticket and was reported immediately after deletion.

Please do not take any action on my remaining project named test.

Thank you for any urgent guidance or escalation.

[Samielakkad]

Keep the support ticket open, but set expectations from the current official documentation: Supabase says a deleted project cannot be recovered, and deletion permanently removes the database, Storage objects, Auth data, Edge Functions, configuration, and platform backups.

• Deletion documentation: https://supabase.com/docs/guides/platform/delete-project
• Backup documentation: https://supabase.com/docs/guides/platform/backups

The ticket is still useful because it records the incident, but upgrading the organization after deletion will not recreate backups that were deleted with the project.

I would stop all automation using this account and do the following before rebuilding:

1. Revoke or rotate the automation access token that authorized the deletion.
2. Preserve the complete CLI output, exact UTC time, deleted project ref, CLI version, ticket number, and Codex transcript for support and the automation-tool maintainers.
3. Search every external source for recoverable artifacts: local or CI supabase db dump files, migrations and seed files in Git, generated schema/types, Edge Function source, Storage copies, analytics exports, downstream data warehouses, and application/provider exports.
4. Recreate from migrations in a new project only after inventorying those artifacts. The new project will have a different project ref, URL, and keys, so update and rotate all application secrets.
5. Add a hard safety gate before any future destructive command: resolve the ref from the project name, print both, require an exact typed confirmation, and refuse deletion when the requested name and returned API name differ.

Do not post the project ref, access token, database credentials, service-role key, or ticket-private information in this public discussion.

The difficult but accurate answer is that recovery now depends on copies outside the deleted Supabase project. The platform's own stored backups are documented as being removed during deletion.