Best of JetBrains — January 2026

1. 1
   Article

   Zed·14w

   The ACP Registry is Live — Zed's Blog

   The ACP Registry is now live, allowing developers to register their AI coding agent once and make it available across all ACP-compatible editors including Zed and JetBrains IDEs. The registry eliminates the need to create separate extensions for each editor, with popular agents like Claude Code, GitHub Copilot CLI, and Gemini CLI already available. Zed is transitioning from its extension-based agent distribution to the registry approach, which enables faster updates without waiting for extension review cycles. JetBrains collaborated on the registry specification as part of their ongoing ACP partnership.

   29

   3
2. 2
   Article

   JetBrains·15w

   Spring Boot Debugging – Now Remote

   JetBrains' Spring Debugger plugin now supports remote debugging without requiring debug agents. The plugin, which has over 300,000 downloads, allows developers to inspect Spring Boot applications running remotely by suspending servlet container threads to read the Spring context. Behavior varies by container: Tomcat loads context immediately, while Jetty and Undertow require the first HTTP request. Setup uses standard JVM remote debugging with an open debug port. Current limitations include embedded-container-only support, required module classpath specification, and no remote database structure view.

   18
3. 3
   Article

   JetBrains·15w

   IntelliJ IDEA 2025.3.2 Is Out!

   IntelliJ IDEA 2025.3.2 has been released with bug fixes addressing terminal flickering when using CLI tools like Claude Code, multiple credential storage and settings synchronization issues in remote development, and improvements to run configuration handling in the Services tool window. The update is available through the IDE, Toolbox App, snaps for Ubuntu, or direct download.

   15
4. 4
   Article

   JetBrains·15w

   Platform Debugger Architecture Redesign for Remote Development in 2026.1

   JetBrains redesigned the IntelliJ Platform debugger architecture in version 2026.1 to support remote development scenarios. The debugger is now split into frontend (UI rendering) and backend (session management) components communicating via RPC. This architectural change deprecates several APIs that directly access debugger UI, introduces asynchronous UI creation, and replaces direct plugin entity access with frontend wrappers. Plugin developers need to migrate from deprecated APIs like `XDebugSession#getUI` and `XDebugSession#getRunContentDescriptor` to alternatives such as `runWhenUiReady` and `XDebuggerTreeBackendOnlyActionBase`. The guide provides two migration paths: local-only mode with minimal changes, or full remote development support requiring more extensive updates.

   10