Jewelry AI - Library
Undo is on the card in the Deleted tab
You deleted a visual, looked for a way back where you deleted it, and there was nothing to press. The restore button sits on the card inside the Deleted tab, and it works on one card at a time.
Where the restore button actually is
Deleting a visual in Jewelry AI is a reversible action, but the control that reverses it is not attached to the moment of deletion. It is rendered on the card itself, in the Deleted tab of the library, which means recovery begins with a change of tab rather than with a press on the notification in front of you (apps/jewelry-mobile/src/app/(tabs)/library.tsx, verified 2026-08-18).
The confirmation you accept before deleting says this: its message tells you the visual can be brought back from the Deleted tab (tr-TR.ts:716, verified 2026-08-18). The promise is made in the dialog; the button that keeps it is in another tab.
After a bulk delete the app shows a notification as well, and that notification has no restore action in it (library.tsx:430-436, verified 2026-08-18). If you are waiting for something to press there, nothing is coming.
What the Deleted tab does, and what it does not do
The Deleted tab holds the same cards you know from the rest of the library, but two of the gestures you use elsewhere are not attached to them.
- Restore is a button on a single card.
- The restore control is rendered per card in the Deleted tab and applies to that card alone (library.tsx, verified 2026-08-18).
- A long press does not start a selection.
- The handler that opens multi-select on a card is not attached while the card is deleted, so the selection mode you use in the other tabs never opens in this one (library.tsx, verified 2026-08-18).
- A tap does not open the card.
- The open handler is removed for deleted records, so you cannot enter the detail view to inspect a visual before deciding what to do with it (library.tsx:106, verified 2026-08-18).
- Permanent delete is a second, separate confirmation.
- It is its own destructive step, with a message stating that it cannot be undone and that the visual and your related files will be permanently deleted (en-US.ts, library.purge.message, verified 2026-08-18).
Deleting many and restoring many are not the same operation
In the normal library tabs a long press starts a selection, and several visuals can be removed together. The Deleted tab has no counterpart to that: with no selection mode on its cards, a batch removed in one action comes back one card and one button press at a time (library.tsx, verified 2026-08-18).
This is the part of the tab worth knowing before you need it. The cost of a bulk delete is not paid when you delete; it is paid if you change your mind, and it grows with the number of visuals rather than with the number of actions you took.
The same asymmetry appears in the notifications: the bulk delete gets one, and it carries no way back (library.tsx:430-436, verified 2026-08-18).
The same card, in the two places it appears
Behaviour read from the library screen of the mobile client, verified 2026-08-18.
| Card behaviour | Normal library tabs | Deleted tab |
|---|---|---|
| Tap the card | Opens the record detail view | Nothing happens (library.tsx:106) |
| Long press the card | Starts a selection with that card | Not available |
| Handle several in one action | A batch delete is possible | No batch restore; restore is per card |
| Status badge | One of three states: processing, completed, failed | The same badge the record already had; there is no deleted state (status-badge.tsx:9-13) |
What a restore gives back
A restored record returns to your normal list carrying the badge it already had. The badge only ever reports processing, completed or failed, and it has no state for a record that was deleted, which is why a card in the Deleted tab looks like any other card apart from its two buttons (status-badge.tsx:9-13; types.ts:145, verified 2026-08-18). There is no intermediate badge such as queued or cancelled.
A restored visual reappears in the collection it was in. How collection membership behaves around deletion is the subject of a separate page and is not described here.
What deletion does to the stored record and to the file behind it is not reported anywhere in this tab. That question belongs to the page on what deleting a result starts, linked below, and nothing here should be read as an answer to it.
Which action fits the situation in front of you
| Situation | Choose | Why |
|---|---|---|
| You deleted one visual by mistake a moment ago. | Move to the Deleted tab and press restore on that card. | The restore control exists only on the card in that tab; the notification you are looking at does not carry it. |
| You removed a batch of catalogue visuals and want all of them back. | Restore them one card at a time in the Deleted tab. | There is no selection mode in that tab, and the notification shown after a bulk delete has no restore action. |
| You want to look at a deleted visual closely before deciding. | Decide from the card as it appears in the list, or restore it first and open it from your normal list afterwards. | A deleted card cannot be opened; the tap that opens a card is not attached while the record is deleted. |
| You are clearing out visuals you are certain you will not need. | Use permanent delete, and read the second confirmation before you accept it. | Its text says the action cannot be undone and that the visual and your related files will be permanently deleted. |
| You are waiting to see whether the Deleted tab empties itself. | Do not plan around that; decide on each card yourself. | The app states no period for how long a deleted visual stays there, and this surface does not report whether anything is removed automatically. |
What this page does not settle
These are boundaries, not omissions. Each one is either owned by another page or not readable from the library screen.
- How long a visual remains in the Deleted tab. The app makes no statement about a period, and it cannot be read from this surface.
- Whether deleted visuals are ever removed without you asking. Not reported here.
- What becomes of the record and of the file after a deletion - that is the subject of the page on what deleting a result starts.
- How selection works in the normal library tabs, including what a select-all covers. Not described here.
- How deleting a collection differs from deleting a single visual. Not described here.
- Anything shown in a web or admin panel: these findings rest on the API and the mobile client only.
Questions
I just deleted a visual and the notification did not offer a way back. Where is it?
On the card, in the Deleted tab of your library. The restore control is rendered there rather than in the notification shown at the moment of deletion, so you have to change tabs to reach it. The confirmation you accepted before deleting says the visual can be brought back from that tab (library.tsx; tr-TR.ts:716, verified 2026-08-18).
Can I restore several deleted visuals at once?
No. The Deleted tab has no selection mode: a long press on a deleted card does not start a selection, and restore is a button on a single card. A batch you deleted in one action has to be restored one card at a time (library.tsx, verified 2026-08-18).
How long do deleted visuals stay in the Deleted tab?
The app does not state a period, and it cannot be read from the library screen. What a deletion sets in motion on the record itself is covered by the separate page on what deleting a result starts; this page makes no claim about timing.
What does permanent delete actually do?
It is a separate second confirmation, distinct from the deletion that put the card in this tab. Its message reads: 'This cannot be undone. The visual and your related files will be permanently deleted.' No further recovery route is described anywhere on this page (en-US.ts, library.purge.message, verified 2026-08-18).