Why IntelliJ IDEA’s New Recycle‑Bin Deletion Changes Matter for Developers

JetBrains released IntelliJ IDEA 2026.1 EAP 3 with many updates, the most noteworthy being the long‑awaited change that now moves deleted files to the operating system’s recycle bin instead of permanently erasing them.

In JetBrains’ issue tracker the request was filed six years ago; previously the IDE’s Project view deletion performed a direct permanent delete, leaving recovery to Local History or Git. The old workflow required developers to rely on Local History or version control, and untracked files were lost.

The issue is now marked State: Fixed and Available in: 2026.1 EAP 3 , meaning the new default behavior is to move files to the recycle bin.

Now deleting a file results in moving it to the recycle bin rather than permanent deletion.

Some developers argue that “Git is enough,” but the article points out that many files are not under version control: newly created uncommitted files, local scripts, SQL files, scratch files, temporary code, and configuration files. When such files are accidentally removed, Git cannot help.

JetBrains has long recommended Local History, yet it has several drawbacks: it can be cleaned automatically, upgrades may purge entries, searching is cumbersome, undo is not always available, and newcomers often do not know where to find it.

Using the OS recycle bin offers clear advantages: it matches user habits, provides a visual interface, works across applications, does not depend on the IDE, and is 100 % intuitive. This is why virtually every editor implements this behavior by default.

The change addresses one of the most common and fatal IDE accidents—accidental file deletion.

Other notable improvements in 2026.1 EAP 3

Spring support : shows injected bean inlays, runtime bean hints in the debugger, API versioning configuration improvements, and automatic SQL dialect detection.

Java enhancements : more javac parameter completions, pattern‑matching diagnostic fixes, and import performance optimizations.

Kotlin updates : deprecation of K1 API, new destructuring‑syntax navigation, and compiler‑generated declaration inlay hints.

Editor experience : smooth cursor animation, rounded cursor shape, terminal experience fixes, and improved plugin management.

AI & command completion : fixes for empty‑text replacement, updated AI command‑completion icons, migration of JavaMemberNameCompletionContributor to ModCommand completion, fixes for command generation in new‑line + tab scenarios, ability to skip meaningless completions, and multiple LLM workflow fixes in the MCP server.

Platform architecture : removal of ProjectExtension, front‑end migration of the AI assistant plugin, LSP null‑safety fixes, support for background write actions, and cleanup of CachedValuesManager.

Performance & stability : fixes for Gradle sync file leaks, VFS recursive loading issues, debugger CPU conflicts, branch‑switch hangs, Git failures, plugin compatibility false‑positives, and over 70 additional known issues.

All these changes are positioned as preparation for “remote IDE + AI IDE + distributed IDE” scenarios, indicating JetBrains’ strategic focus on collaborative and AI‑assisted development environments.