Delete nodes safely

Deleting a graph node starts a reversible deletion. Convography immediately hides the selected conversational turn and every reply below it, returns selection to the parent when possible, and waits seven seconds before permanent cleanup.

Delete a non-root node#

1. Select the node you intend to remove.
2. Use the toolbar trash action or open the node menu and choose Delete.
3. Read the confirmation. It names the node and warns that replies below it are included.
4. Confirm only after checking the descendants on the graph.

If the selected visual node represents an assistant answer paired with its user prompt, deletion starts at the corresponding user turn so the graph is not left with a broken half-exchange.

Root deletion#

Deleting the root is equivalent to deleting the conversation. The confirmation asks whether to remove the conversation and all of its messages. This removes it from the conversation pane.

Related files#

When messages are deleted, Convography evaluates files related to that subtree. Files that are no longer referenced can be cleaned up with the deleted work. Do not assume every exported or generated artifact will survive a subtree deletion; download anything you must keep first.

Synthesis sources and active workflows#

Deleting a synthesis node removes that result and its ordinary descendants but leaves its selected source branches in place. Deleting a source node is different: the affected set also includes synthesis results that depend on that source and any descendants below those results. Read the confirmation and graph carefully because a source can influence a result outside its ordinary parent-child subtree.

If the deleted area contains optimistic provider or synthesis nodes that are still running, the workspace removes those temporary nodes instead of repainting stale work after the server accepts the deletion. Completed work outside the deletion boundary remains available.

Undo before cleanup#

After confirmation, an Undo notice reports how many graph nodes were deleted and counts down for seven seconds. A paired prompt and response are one graph node in this count. Choose Undo before the deadline to restore the conversation or subtree. The countdown and undo action survive a reload because the server, not the browser, owns the deadline.

Hidden content is immediately absent from graph, chat, search, file-context, and public-share reads. The messages and related records remain recoverable only during the countdown. After it expires, a background cleanup job permanently purges them and removes conversation files that no surviving node references. User-library files remain independent.

If you delete a descendant and then delete one of its ancestors during the Undo window, Convography expands the existing reversible deletion instead of reporting an overlap error. Several intersecting pending deletions become one Undo notice, and using any still-visible receipt restores the combined set. Deleting the whole conversation absorbs its pending subtree deletions and restarts the seven-second window. Unrelated pending deletions stay independent unless a later deletion joins their affected sets.

If you need a longer-lived safety copy:

• split the path into a new conversation before deleting;
• export important responses;
• download generated or uploaded files;
• create a share only for collaboration, not as a private backup. A share cannot keep pending-deletion content available.

If deletion fails#

The dialog remains available with an error message. Do not repeatedly click the action. Close the dialog, refresh the graph to verify current state, and try once more. If an Undo action reports that its deadline expired, refresh to see the permanent state. Contact support with the conversation title, approximate node title, and time of the attempt—never include a share token or password.