Delete from everywhere

Delete from everywhere is what to use when you really mean it. The file gets removed from your Mac (to Trash) and from every destination it's on (cloud objects deleted via API; drive copies removed). After this action, the file is gone unless you can recover it from your macOS Trash before emptying.

The action is per-file. There's no project-wide equivalent for this one (and there won't be). If you want to wipe a whole project everywhere, do it project by project, file by file.

When this is the right call

• You shot something you can't legally retain (privacy, contractual).
• You shot something that's embarrassingly bad and want it gone everywhere.
• You uploaded the wrong file to the wrong project and want it removed from every backup.
• You're cleaning up a long-running archive and want individual outdated files gone for good.

How to do it

Open the file's row in the project file table, click the three-dot menu, choose Delete from everywhere. Tusk shows a confirmation modal that lists:

• The file name and full path.
• Every destination it will be deleted from.
• The local copy (if present).
• A type-to-confirm field with the exact file name.

Type the file name exactly as shown to enable the Delete button, then click it. Tusk runs the deletions in parallel across all destinations and updates the file table.

What happens to each location

• Local copy: moved to the macOS Trash (recoverable until you empty Trash, then gone).
• External drive copies: deleted from the drive's filesystem. If the drive is currently connected, the deletion happens immediately. If the drive is disconnected, Tusk queues the delete and runs it the next time the drive is connected.
• Cloud copies: deleted via the provider's API. For S3-compatible providers, this is a DeleteObjectcall. For Google Drive, a file move-to-trash followed by a permanent delete (Drive doesn't support immediate hard-delete via thedrive.file scope). The behavior is logged per destination so you know exactly what happened where.

What if a destination is offline?

The action proceeds against the destinations that are reachable, and queues the delete against the others for when they come back. Tusk surfaces a notification listing the queued destinations so you know the action isn't fully complete yet. Reconnect the drive (or wait for the cloud destination to recover) and Tusk finishes the job automatically.

What happens to the file index entry?

After every destination has confirmed the delete (and the local copy is gone), Tusk removes the file from the project's index. The row disappears from the file table. Tusk no longer tracks the file. If a copy somehow re-appears later (someone restores it from Trash, a versioned cloud bucket undeletes it), Tusk treats it as a new file the next time it sees it.

If a destination's delete fails (e.g. cloud API returned a permission error), Tusk surfaces it as an error and keeps the file in the index. Fix the underlying issue and run the action again.