Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>Remote TrashNew to Visual Studio Code? Get it now.
Remote Trash

Remote Trash

Zwyx

zwyx.dev
|
2 installs
| (0) | Free
Move files to trash in dev containers.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Remote Trash

VS Code doesn't support moving files to the trash when working in a remote environment like dev containers. This extension adds a Delete option to the file explorer context menu that moves files to the trash using a CLI tool like trash-cli.

VS Code's file explorer inside a dev container:

Without this extension:

File explorer context menu without extension - no delete option available

With this extension:

File explorer context menu with extension - Delete option available

Installation

This extension requires a trash CLI tool to be installed in your dev container. The most commonly used tool is trash-cli.

Manual Installation in a Running Container

To install trash-cli in an already running container, use docker exec from your host machine. Example with a Debian/Ubuntu-based container:

docker exec -it --user root <container-name> bash -c "apt-get update && apt-get install -y trash-cli && rm -rf /var/lib/apt/lists/*"

Replace <container-name> with your container's name or ID (find it with docker ps).

Adding to Dev Container Configuration

To automatically install trash-cli when your dev container is created, add it to your .devcontainer/devcontainer.json:

{
	"postCreateCommand": "sudo apt-get update && sudo apt-get install -y trash-cli && sudo rm -rf /var/lib/apt/lists/*",
	"customizations": {
		"vscode": {
			"extensions": ["zwyx.remotetrash"]
		}
	}
}

With a Dockerfile

Add this to your Dockerfile:

RUN apt-get update && apt-get install -y trash-cli && rm -rf /var/lib/apt/lists/*

Settings

remotetrash.trashCliPath

Path or command for the trash CLI executable. Defaults to trash.

If you're using a different trash utility or need to specify a full path, you can customize this setting.

Limitations

No integration with the file explorer undo stack

After deleting a file with this extension, you cannot do Edit → Undo to undo the deletion. You'll need to use the terminal with trash-restore (part of trash-cli) to restore your file. Hopefully, you'll find this still better than having lost your file permanently.

The reason is that VS Code has separate undo stacks for the editor and the file explorer, and unfortunately, extensions only get access to the editor one (WorkspaceEdit, which isn't of much use for us, since deleting a file closes its editor).

Deleting files with the keybinding (Delete) clears the formatting of your clipboard content

Yes, you've read correctly.

Using the clipboard as an intermediary is the only way for extensions to retrieve the list of selected files from the file explorer. There is an open issue about this.

When you press Delete, this extension saves the content of your clipboard, copy the list of selected files, retrieves it from the clipboard, and restores the original content of your clipboard. Unfortortunately, only the text is restored, any formatting is lost.


Because of these limitations, a feature request for a better support of the trash in dev containers has been open.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2025 Microsoft