The delete we couldn't put a dialog in front of

When an assistant can delete a folder for you, a confirm dialog is no longer available as a safety net. LUVI's answer was to defer the delete by 24 hours instead — and to leave the folder's contents exactly where they were, so restoring it is an undo rather than a cleanup job.

Published:

A glowing amber folder hangs in the air above an open, empty drawer, held there by a thin ring of teal light.

Deleting a folder in LUVI is not final. It waits 24 hours, and within that window it can be brought back with its subfolders and its path intact. That behavior is newer than the folder feature itself, and the reason it exists says something about building for assistants rather than only for people.

A confirm dialog needs someone to confirm

For as long as the only way to delete a folder was clicking in the app, a confirmation dialog was enough of a guard. Then the LUVI connector gained a delete_folder tool, and an assistant could do it on your behalf.

The protocol that connectors speak does have a mechanism for this — the server can ask the client to put a question in front of the user before an irreversible step. But a server only gets to ask if the client says it supports asking, and the assistant most people connect LUVI to does not declare that capability. The dialog would simply never appear.

So the guard could not be a question. It had to be time.

What the trash actually does

Deleting a folder stamps it and every folder under it with one timestamp. From that moment the folder is invisible and unwritable: it disappears from the list, nothing can be generated or uploaded into it, and you cannot create a new folder inside it.

The part worth pausing on is what does not happen. The files inside keep pointing at that folder. They are not moved, not re-sorted, not re-tagged — they simply become visible at the project root while the folder is away, so nothing you made is hidden from you in the meantime.

That is the whole difference between an undo and a cleanup. The older behavior scattered a folder's contents to the root and then dropped the folder, which meant that even if you kept a record of the deletion you could not put the folder back the way it was — you would be re-filing by hand. Leaving the contents attached is what makes restore faithful.

Restore also brings back the path. A folder cannot be reachable while a folder above it is still in the trash, so restoring a child brings its parents with it.

24 hours, and then it means it

An hourly job takes over after the window closes. It does what the old delete did: the contents detach to the project root, and the folder itself is removed. The files themselves are untouched — they keep their own lifecycle, and they stay in your library.

The same 24 hours applies in two other places you can see. A deleted project sits in the Projects trash with Restore, Restore all and Empty trash. A deleted file sits in the Library's Trashcan, stops counting against your storage immediately, and can be restored or purged early from the same toolbar.

Deleting your account is the one that isn't 24 hours: that grace period is 14 days, and it is undone with a link we email you rather than a button in the app.

Where the button is

The folder waits in the Library's Trash, next to deleted files, with a countdown of the time it has left. Restore puts it back with its subfolders, and Delete permanently ends the wait early. Its contents never go there: they are already in front of you at the project root, so what you lose in those 24 hours is the arrangement, not the work.

From the assistant you connected, the same restore is a restore_folder call. The help center covers the full behavior — folders, projects and single files — in how to delete or restore a folder or project.

Why this is the right shape

There is a temptation, when an assistant can do something irreversible, to make it ask more. But asking is a capability the other side has to support, and it is the one thing you cannot rely on across every client that might connect.

Deferring the action is different: it works regardless of who asked, whether they were paying attention, and whether any dialog was available. Nobody has to be told about it for it to protect them, which is the property you want from a guard on an irreversible step.

How we checked

  • What was read: LUVI's own folder trash implementation and its hourly purge job, the delete and restore behavior for projects and library files, and the account deletion grace period.
  • Date: September 22, 2026, re-checked October 20, 2026.
  • Results: a 24-hour window for folders, projects and single files, each purged by an hourly job; folder contents left attached during the window; restore covering the subtree and the ancestor path, from the Library's Trash or with restore_folder; a 14-day window for account deletion.
  • Drawbacks: this describes the behavior as built. No outputs were generated for this post, and it makes no claim about how often anyone actually uses the window.

In LUVI

If you delete a folder and change your mind, the files are already at the project root, and the folder waits in the Library's Trash for the next 24 hours. If you delete a project or a file, open the trash on that page and press Restore.

New accounts start with 200 credits, and verifying a phone and a card adds up to 1,500 more. You can create a LUVI account and organize without worrying that one wrong click costs you an afternoon of filing.

More from Inside LUVI