# IntelliJ IDEA IntelliJ IDEA is an intelligent, context-aware IDE for working with Java and other JVM languages like Kotlin, Scala, and Groovy on all sorts of applications. This environment is used especially for the development of programs. It has features like advanced code navigation, ability to refactor codes, and advanced error checking features which allows faster and easier error checking. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Logpoints Walkthrough DevFeed: [Logpoints Walkthrough]() Original publisher: [Read original article]() Author: Igor Kulakov Published: 2026-09-16T14:14:04Z Content type: tutorial Language: en Sources: [The JetBrains Blog]() Topics: [IntelliJ IDEA](), [debug](), [debugging](), [gRPC](), [Java](), [2026.2]() Tags: [2026-2](), [bug](), [client](), [command-line](), [debug](), [debugger](), [debugging](), [debugging-tools](), [idea](), [intellij](), [intellij-idea](), [java](), [kotlin](), [logpoints]() ### AI overview This walkthrough explains how to use logpoints in IntelliJ IDEA to investigate a bug in a gRPC client-server example that returns incorrect discount values. It covers reproducing the issue, attaching the debugger to the server, and observing program behavior without suspending execution, including improvements in IntelliJ IDEA 2026.2. ### Source excerpt Modern development tools, especially IntelliJ IDEA, have such comprehensive debugging support that for virtually any niche use case, there is a specialized tool for the job. This can make it hard to know where to begin. If you are new to debugging tools and want the biggest return on your learning investment, the best feature [...] ## IntelliJ IDEA 2026.2.3 Is Out! DevFeed: [IntelliJ IDEA 2026.2.3 Is Out!]() Original publisher: [Read original article]() Author: Maria Kosukhina Published: 2026-09-16T10:53:53Z Content type: release Language: en Sources: [The JetBrains Blog]() Topics: [IntelliJ IDEA](), [2026.2](), [Release notes](), [releases](), [Maven](), [Markdown](), [plantuml](), [WSL2](), [Ubuntu]() Tags: [2026-2](), [intellij-idea](), [markdown](), [maven](), [plantuml](), [release-notes](), [ubuntu](), [wsl2]() ### AI overview JetBrains released IntelliJ IDEA 2026.2.3 with fixes and improvements affecting Maven project data, IDE freezes, Markdown preview scrolling, PlantUML support, and applications using WSL2 mirrored networking. ### Source excerpt We've just released IntelliJ IDEA 2026.2.3. You can update to this version from inside the IDE, using the Toolbox App, or using snaps if you are a Ubuntu user. You can also download it from our website. The latest update brings the following improvements: For a comprehensive overview of the fixes, see the release notes. [...] ## Java 27 in IntelliJ IDEA DevFeed: [Java 27 in IntelliJ IDEA]() Original publisher: [Read original article]() Author: Marit van Dijk Published: 2026-09-15T14:49:02Z Content type: tutorial Language: en Sources: [The JetBrains Blog]() Topics: [IntelliJ IDEA](), [Java](), [JDK 27]() Tags: [intellij-idea](), [java](), [java-27](), [jdk-27](), [news]() ### AI overview A tutorial on using Java 27 with IntelliJ IDEA, including downloading or configuring JDK 27 and setting the project language level. ### Source excerpt In line with the six-month release cadence, Java 27 was released on September 15, 2026. In this blog post, we will look at what's included in this release, how IntelliJ IDEA continues to support the latest Java versions, and even how IntelliJ IDEA is benefiting from some of the changes to the JDK. Java 27 [...] ## The Evolution of WSL Support in JetBrains IDEs DevFeed: [The Evolution of WSL Support in JetBrains IDEs]() Original publisher: [Read original article]() Author: Kristina Pchelintseva Published: 2026-09-09T10:39:49Z Content type: article Language: en Sources: [The JetBrains Blog]() Topics: [IntelliJ IDEA](), [Processes]() Tags: [2026-2](), [architecture](), [debug](), [ecosystem](), [engineering](), [ide](), [idea](), [intellij-idea](), [intellij-platform](), [linux](), [phpstorm](), [remote-development](), [support](), [webstorm](), [windows](), [wsl]() ### AI overview JetBrains describes its evolution of WSL integration and recommends Native mode from version 2026.2. In this mode, supported IDEs remain Windows applications while an agent in WSL handles project files and processes. ### Source excerpt JetBrains IDEs have worked with WSL for many years, and over time, several ways of using it have emerged across our products. Depending on the entry point, the IDE could rely on a different underlying architecture, leading to a different experience. Starting with the 2026.2 release, there is one recommended entry point. In IntelliJ IDEA, [...] ## Debug Past an HTTP 403 Without Breaking Spring Security DevFeed: [Debug Past an HTTP 403 Without Breaking Spring Security]() Original publisher: [Read original article]() Author: Andrey Belyaev Published: 2026-09-08T12:34:18Z Content type: tutorial Language: en Sources: [The JetBrains Blog]() Topics: [debug](), [Authorization](), [IntelliJ IDEA](), [ide]() Tags: [debug](), [features](), [http](), [intellij-idea](), [security](), [spring](), [spring-debugger](), [tutorials]() ### AI overview The article explains how IntelliJ IDEA security inlays help debug Spring endpoints blocked by HTTP 403, 401, or login redirects. It covers inspecting runtime role requirements and temporarily unlocking an endpoint for a debug session, with a warning that unlocking affects all clients reaching that URI and method. ### Source excerpt You set a breakpoint inside a Spring MVC controller, or a service, send the request to an HTTP endpoint, and nothing happens. The response is back - and it is a 403 (or 401, or a redirect to a login page). At that point, the bug you were trying to catch is no longer the [...] ## Java Weekly, Issue 662 DevFeed: [Java Weekly, Issue 662]() Original publisher: [Read original article]() Author: baeldung Published: 2026-09-06T09:25:19Z Content type: article Language: en Sources: [Baeldung]() Topics: [IntelliJ IDEA](), [Concurrency](), [Tooling](), [Cryptography](), [elasticsearch]() Tags: [concurrency](), [cryptography](), [elasticsearch](), [intellij-idea](), [java](), [no-ads](), [no-after-post](), [no-before-post](), [no-optins](), [tooling](), [weekly-review](), [weekly-review-no-ads-no-after-post-no-before-post-no-optins]() ### AI overview A Java ecosystem roundup led by a hands-on look at Project Loom in IntelliJ IDEA, covering virtual threads, scoped values, structured concurrency, and related tooling. It also links to Java and Spring articles, podcasts, release announcements, code-review commentary, and IntelliJ IDEA Conf 2026. ### Source excerpt The three Loom pillars and, more importantly, the tooling. Plus IntelliJ IDEA Conf 2026 getting close. The post Java Weekly, Issue 662 first appeared on Baeldung. ## Java Weekly, Issue 661 DevFeed: [Java Weekly, Issue 661]() Original publisher: [Read original article]() Author: baeldung Published: 2026-08-26T17:15:42Z Content type: article Language: en Sources: [Baeldung]() Topics: [IntelliJ IDEA](), [Spring Boot 4](), [Orchestration](), [Quarkus](), [elasticsearch](), [JSON](), [Compiler](), [Scripting](), [GUI](), [Cryptography](), [Security]() Tags: [boot](), [cryptography](), [gui](), [intellij](), [intellij-idea](), [java](), [json](), [metrics](), [netflix](), [no-ads](), [no-after-post](), [no-before-post](), [no-optins](), [orchestration](), [post](), [release](), [scripting](), [security](), [weekly-review](), [weekly-review-no-ads-no-after-post-no-before-post-no-optins]() ### AI overview Java Weekly, Issue 661 is a roundup covering IntelliJ IDEA Conf, the JDK 27 release candidate, early JDK 28 developments, Spring and Java updates, technical articles, webinars, and recent framework and library releases. It also highlights Netflix Conductor's evolution as a workflow orchestration engine. ### Source excerpt IntelliJ IDEA Conf is back, JDK 27 got its first RC and JDK 28 is already looking solid The post Java Weekly, Issue 661 first appeared on Baeldung. ## Resilient Sync: Your IDE Keeps Helping even when your Build is Broken DevFeed: [Resilient Sync: Your IDE Keeps Helping even when your Build is Broken]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2026-08-13T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [IntelliJ IDEA](), [ide](), [2026.2](), [configuration]() Tags: [2026-2](), [autocomplete](), [build](), [feature](), [gradle](), [ide](), [intellij-idea](), [kotlin](), [upgrade]() ### AI overview Gradle 9.7 and IntelliJ IDEA 2026.2 introduce resilient sync, allowing the IDE to remain useful when parts of a Gradle build fail to configure. Instead of aborting the entire sync, Gradle provides partial project models, editor data for resolvable Kotlin DSL scripts, and structured failure information. ### Source excerpt You upgrade Gradle, hit sync, and watch every build script turn red. The IDE that was finishing your sentences five minutes ago suddenly has nothing to say, and you're left fixing build logic in what is effectively a very expensive text editor. And the API you need to fix the error is the exact API the IDE can no longer tell you anything about. To get autocomplete back, fix the build. To fix the build, it would help to have autocomplete. Chicken, meet egg. Gradle 9.7, together with IntelliJ IDEA 2026.2, fixes this. The feature is called resilient sync, and it is one of those changes you only notice by its absence once you have it. What goes wrong today Nobody designed the old behavior to be cruel. It falls out of two entirely reasonable decisions that happen to collide. The IDE reasons that if it cannot get a model back from Gradle, it has nothing accurate to show you, so it shows almost nothing. Gradle reasons that if configuration throws, the whole operation failed, so it reports the failure and stops. Both are correct. Together they produce a tool that abandons you precisely when you need it most. The worst version is the multi-project build. You have a hundred subprojects, and one of them (or one shared convention plugin in an included build) has a broken script. In the old world, that single failure takes down the sync for all one hundred. Ninety-nine healthy projects lose their IDE support over one bad line somewhere else in the tree. Power users had a workaround, as charming as workarounds usually are: # The old "please just give me some completion" incantation. Don't rely on this. org.gradle.jvmargs=-Dorg.gradle.kotlin.dsl.provider.mode=classpath It coaxed some completion out of a broken build, frequently broke Gradle's internal state in other ways, and often needed an IDE restart to load new API. Reader, it was not a fix. It was a coping mechanism. What is resilient sync? Resilient sync replaces all-or-nothing with best-effort. When part of your build fails ## KotlinLLM is Going Open Source DevFeed: [KotlinLLM is Going Open Source]() Original publisher: [Read original article]() Author: Anastasia Birillo Published: 2026-07-28T07:50:41Z Content type: article Language: en Sources: [Kotlin : A concise multiplatform language developed by JetBrains | The JetBrains Blog]() Topics: [kotlinllm](), [Kotlin](), [Open Source](), [IntelliJ IDEA](), [Large Language Model](), [Code generation](), [AI-assisted coding](), [Software Engineering]() Tags: [code-completion](), [code-generation](), [engineering](), [intellij](), [intellij-idea](), [kotlin](), [kotlinllm](), [llm](), [llms](), [open-source](), [plugin](), [research](), [research-prototype](), [software](), [software-engineering]() ### AI overview KotlinLLM is an open-source research prototype and IntelliJ IDEA plugin for Kotlin/JVM projects. It introduces Smart macros whose generated Kotlin source evolves from runtime scenarios, allowing applications to delegate selected logic to an LLM without calling the model on every request or relying on a separate runtime agent. ### Source excerpt TL;DR KotlinLLM is now public. It's a research prototype for delegating runtime logic to an LLM from Kotlin code. Instead of calling an LLM on every request or running a separate agent, you can write an explicit Kotlin call. Its body is generated Kotlin source code, and that code is updated as your application hits [...] ## Live coding with dir stepper DevFeed: [Live coding with dir stepper]() Original publisher: [Read original article]() Published: 2026-07-16T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [intellij-platform](), [IntelliJ IDEA](), [Git](), [ide](), [Code](), [Documentation]() Tags: [code](), [coding](), [git](), [ide](), [intellij-idea](), [intellij-platform](), [kotlinconf](), [plugin](), [presentation](), [procedural](), [refactoring]() ### AI overview The article describes creating a workflow for live-coding presentations after finding that Git commits and interactive rebases were cumbersome for managing sequential coding steps. It explores using IntelliJ IDEA as an extensible platform for a tool that can move through steps, jump to completed states, refactor steps, and keep the process unobtrusive for the presenter and audience. ### Source excerpt Two months ago I gave my first ever live programming talk at KotlinConf. It was called "Talking to terminals (and how they talk back)", and you can watch it here. I've previously done slide-heavy talks which contained small demos or navigating through an existing codebase. Since this talk was starting from nothing, I decided to just write all the code from nothing. This meant spending the majority of the time in the IDE, but also figuring out how to remember what I was supposed to be writing at each step. Making the wrong choice The exceedingly obvious solution to having a series of steps in a live coding presentation is a git repo and a commit for each step. Unfortunately, this is a huge pain in the ass and really doesn't work at all (at least not for me). I started with commits, but by the 7th or 8th commit I was spending more than half my time doing interactive rebases over the entire history. Need a function in step 8 that should've been extracted between step 3 and 4? That's another 10 minutes rewriting history. Because it's a small set of files that are changing, every commit conflicts with any changes to history. It's also not clear how you actually move through the history. We want to start from nothing and move forward through history. Generally, git helps you jump backwards from the latest, not stepping forward from the oldest. It's not impossible, it's just clearly going against the grain. The problem, defined Now thoroughly enjoying this distraction from writing the actual talk, I distilled what I was trying to solve. Ability to manually write the changes required or to simply jump to the finished step. Some steps are important to watch unfold while others are procedural. This also can help with time management when I (inevitably) run low on time. Easily refactor steps as I go. Later steps often requiring refactoring previous ones to minimize the diff. As the talk evolves I want to add or merge steps. Nearly invisible to me and the viewer. I don't want t ## A Real IntelliJ IDEA Inside Docker: Integration Tests with X Server, Window Manager, and Live Video DevFeed: [A Real IntelliJ IDEA Inside Docker: Integration Tests with X Server, Window Manager, and Live Video]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-07-05T00:00:00Z Content type: tutorial Language: en Sources: [Eugene Petrenko]() Topics: [IntelliJ IDEA](), [Docker](), [Testing](), [Docker Container](), [FFmpeg (Fast Forward Moving Picture Experts Group)](), [GUI](), [Node.js](), [MCP]() Tags: [ai-agents](), [ai-coding](), [browser](), [devrig](), [docker](), [docker-container](), [eugene-petrenko](), [ffmpeg](), [gui](), [intellij](), [intellij-idea](), [jonnyzzz](), [mcp](), [mcp-steroid](), [node-js](), [plugin](), [tag-41199d53f463](), [testing](), [tests]() ### AI overview This tutorial presents a reusable approach for running full IntelliJ IDEA integration tests inside Docker with a GUI. It covers the container image, X server, window management, IDE control, and streaming live video to a browser, with open-source code in the test-integration module. ### Source excerpt Evals that boot a full IntelliJ IDEA -- pixels, dialogs, indexing and all -- inside a Docker container. Xvfb provides the display, fluxbox keeps the windows in place, ffmpeg records everything, and a tiny Node.js server streams the live video straight into a browser tab on your machine. Here is the whole recipe, so you can build your own. ## Codename One Adds Native macOS Builds and Desktop Integration DevFeed: [Codename One Adds Native macOS Builds and Desktop Integration]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-06T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [macOS](), [iOS](), [Xcode](), [IntelliJ IDEA]() Tags: [apple](), [build](), [desktop](), [ios](), [mac](), [native](), [notifications]() ### AI overview Codename One 7.0.250 adds a native macOS application target that builds from the existing iOS pipeline without bundling a JVM. Desktop integration also adds native window chrome, menus, interactive scrollbars, and notifications, while Mac signing remains an infrastructure gap. ### Source excerpt The same Codename One project can now build a REAL native Mac app through the iOS pipeline, and a deeper desktop layer gives it a real title bar, a native menu bar, interactive scrollbars, and desktop notifications. ## devrig: MCP Steroid Goes Level 3 -- Autonomous IDE Setup for AI Agents DevFeed: [devrig: MCP Steroid Goes Level 3 -- Autonomous IDE Setup for AI Agents]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-06-02T00:00:00Z Content type: article Language: en Sources: [Eugene Petrenko]() Topics: [Model Context Protocol (MCP)](), [AI Agent](), [IntelliJ IDEA](), [Command-line interface](), [Claude](), [Keycloak]() Tags: [agent](), [agentic-experience](), [ai-agent](), [ai-agents](), [ai-coding](), [claude](), [cli](), [devrig](), [eugene-petrenko](), [intellij](), [jonnyzzz](), [keycloak](), [mcp](), [mcp-steroid](), [tag-41199d53f463]() ### AI overview The article presents Level 3 of MCP Steroid, where the devrig CLI autonomously configures an agent's MCP connection and downloads or starts an IntelliJ-family IDE. Its end-to-end test reports that Claude found 4,633 PSI usages of a class in Keycloak in one prompt. ### Source excerpt The new `devrig` CLI in MCP Steroid 0.100 turns the IDE bring-up ritual into one stdio command. `devrig install ` writes the MCP config; `devrig backend download/start` brings an IntelliJ-family IDE into existence and gives the agent an IDE of its own. In the e2e test, Claude provisions an IDE and finds 4,633 PSI usages of one class in Keycloak -- in one prompt. ## On-Device Debugging And JUnit 5 DevFeed: [On-Device Debugging And JUnit 5]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-05-30T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [debugging](), [IntelliJ IDEA](), [Android](), [iOS](), [ide](), [simulator](), [Tooling](), [Code](), [Emulator](), [SDK](), [Visual Studio Code]() Tags: [android](), [android-apps](), [android-studio](), [apk](), [app](), [breakpoint](), [build](), [code](), [debugging](), [developer](), [emulator](), [ide](), [intellij](), [intellij-idea](), [ios](), [java](), [junit](), [linux](), [on-device](), [simulator]() ### AI overview This tutorial describes Codename One's new JDWP-based on-device debugging for ParparVM iOS and Android apps. It explains debugging Java code and objects on simulators and physical devices using IntelliJ IDEA or other JDWP-speaking debuggers, and briefly covers standard JUnit 5 integration with the JavaSE simulator. ### Source excerpt A walk-through of the new JDWP-based on-device debugging pipeline for ParparVM iOS apps and Android apps, with a step-by-step IntelliJ tutorial for each, and a short tutorial on the new standard JUnit 5 integration against the JavaSE simulator. ## From HTTP MCP to stdio: Lessons Connecting an AI Agent to a Desktop IDE DevFeed: [From HTTP MCP to stdio: Lessons Connecting an AI Agent to a Desktop IDE]() Original publisher: [Read original article]() Author: Eugene Petrenko Published: 2026-05-20T00:00:00Z Content type: article Language: en Sources: [Eugene Petrenko]() Topics: [Model Context Protocol](), [IntelliJ IDEA](), [AI Agent](), [Command-line interface](), [Cross-origin resource sharing (CORS)]() Tags: [agentic-coding](), [ai-agent](), [ai-agents](), [ai-coding](), [architecture](), [claude](), [cli](), [codex](), [devrig](), [docker-image](), [eugene-petrenko](), [integration-test](), [intellij](), [jonnyzzz](), [kotlin](), [ktor](), [mcp](), [mcp-steroid](), [report](), [tag-41199d53f463]() ### AI overview This article explains why an HTTP MCP server embedded in a desktop IntelliJ application proved unreliable on real workstations. It describes moving to stdio with a CLI coordinator called devrig, and emphasizes integration tests for the MCP layer, including issues involving dynamic ports, startup ordering, multiple IDEs, and mismatched transport support. ### Source excerpt The obvious way to connect an AI Agent to a running IntelliJ is an HTTP MCP server inside the IDE. I built it, shipped it, and used it daily -- and it kept breaking on real workstations: dynamic ports, start-order lottery, multiple IDEs, and the agent-up/IDE-down dead end. Here is why I moved the whole thing to stdio and a CLI coordinator called devrig, and what the journey taught me. ## Collection Literals in Kotlin DevFeed: [Collection Literals in Kotlin]() Original publisher: [Read original article]() Published: 2026-05-04T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [Collections](), [Compiler](), [IntelliJ IDEA](), [Gradle]() Tags: [collection](), [compiler](), [feature](), [gradle](), [intellij-idea](), [kotlin](), [new-feature](), [workshop-learning-programming]() ### AI overview This tutorial explains Kotlin collection literals, an experimental feature that uses square brackets to create lists, sets, and custom collections. It covers usage examples, compiler requirements, current IntelliJ IDEA limitations, and the expected future support. ### Source excerpt The new feature in Kotlin that allows for concise and expressive collection creation. ## IntelliJ's New Kotlin Coroutine Inspections, Explained DevFeed: [IntelliJ's New Kotlin Coroutine Inspections, Explained]() Original publisher: [Read original article]() Published: 2026-03-30T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [IntelliJ IDEA](), [Kotlin](), [kotlin-coroutines](), [Coroutines](), [Android Studio](), [Exception]() Tags: [android-studio](), [exceptions](), [intellij-idea](), [kotlin](), [kotlin-coroutines](), [workshop-learning-programming]() ### AI overview This article explains new Kotlin coroutine inspections introduced in IntelliJ IDEA and also available in Android Studio. It describes warnings for coroutine usage patterns, including preferring awaitAll over await and currentCoroutineContext() over coroutineContext. ### Source excerpt Exploration and explanation of new Kotlin coroutine inspections in IntelliJ IDEA. ## How I'm Using Agents for Development - January 2026 DevFeed: [How I'm Using Agents for Development - January 2026]() Original publisher: [Read original article]() Author: Sam Edwards Published: 2026-01-07T16:23:40Z Content type: opinion Language: en Sources: [Handstand Sam]() Topics: [Development](), [Claude](), [IntelliJ IDEA](), [ide](), [context window](), [Compose](), [GUI](), [YAML](), [Test automation]() Tags: [agents](), [claude](), [code](), [compose](), [context-window](), [development](), [gui](), [ide](), [idea](), [intellij](), [intellij-idea](), [junit](), [review](), [test-automation](), [updates](), [yaml]() ### AI overview A developer describes using agents with IntelliJ IDEA, Firebender, and Claude Sonnet 4.5 across Trailblaze projects. The article explains a Research, Plan, Implement workflow, including incremental commits, progress handoffs when the context window fills, refactoring, UI test automation, and building a Compose-based YAML editor. ### Source excerpt I'm currently sitting here with Intellij IDEA IDE open with 3 workspaces (different clones of the Trailblaze project). In each one of them I'm using Firebender with the Claude Sonnet 4.5 model. As I'm writing this I just toggled back over to IDE and made sure all my agents are still running. I've been hesitant [...] ## Standardize with ⌘ O ⌘ P to reduce cognitive load DevFeed: [Standardize with ⌘ O ⌘ P to reduce cognitive load]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2025-11-01T00:38:50Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [macOS](), [Obsidian](), [Android Studio](), [IntelliJ IDEA](), [cursor](), [ide]() Tags: [android-studio](), [cognitive-load](), [cursor](), [ide](), [intellij](), [keyboard](), [macos](), [notes](), [shortcuts]() ### AI overview The author recommends standardizing ⌘ O for opening a file or note and ⌘ P for opening a command palette across macOS apps such as Obsidian, Android Studio, IntelliJ, and Cursor. They report that using consistent shortcuts reduces the need to remember app-specific commands and helps build muscle memory. ### Source excerpt There are a few apps on macOS in the text manipulation category that I end up spending a lot of time on. For example: Obsidian (for notes), Zed (text editor + IDE lite), Android Studio & Intellij (IDE++), Cursor (IDE + AI), etc. All these apps have two types of commands that I frequently use: Open a specific file or note Open the command palette (or find any action menu) But by default, these apps use ever so slightly different shortcuts. One might use ⌘ P, another might use ⌘ ⇧ P, etc. I've found it incredibly helpful to take a few minutes and make these specific keyboard shortcuts the same everywhere. So now I use: ⌘ O - Open a file/note ⌘ P - Open the command palette (or equivalent action menu) This small change has reduced cognitive load significantly. I no longer have to think about which app I'm in, and what the shortcut is for that specific app. Muscle memory takes over, and I can just get things done faster. Highly recommended! ## ACP Brings JetBrains on Board DevFeed: [ACP Brings JetBrains on Board]() Original publisher: [Read original article]() Author: Franciska Dethlefsen Published: 2025-10-06T00:00:00Z Content type: release Language: en Sources: [Zed Industries - Blog]() Topics: [Protocol (disambiguation)](), [ide](), [IntelliJ IDEA](), [junie](), [PyCharm](), [webstorm](), [codex]() Tags: [codex](), [gemini](), [integration](), [integrations](), [intellij](), [intellij-idea](), [jetbrains](), [junie](), [protocol](), [pycharm](), [vendor-lock-in]() ### AI overview JetBrains will co-develop the Agent Client Protocol with Zed and plans to add ACP support across its IDE ecosystem, including IntelliJ IDEA, PyCharm, and WebStorm. The article presents ACP as an open standard intended to let agents work across compatible editors. ### Source excerpt The Agent Client Protocol reaches a major milestone: JetBrains is committing to bringing ACP support to their entire ecosystem. ## Setting up Compose Multiplatform previews DevFeed: [Setting up Compose Multiplatform previews]() Original publisher: [Read original article]() Author: Márton Braun Published: 2025-07-29T07:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [compose-multiplatform](), [Kotlin Multiplatform](), [Android Studio](), [IntelliJ IDEA](), [Tooling]() Tags: [android](), [android-studio](), [compose-multiplatform](), [how-to](), [intellij](), [intellij-idea](), [kmp](), [kotlin](), [marton-braun](), [multiplatform](), [tooling](), [zsmb](), [zsmb-co](), [zsmb13](), [zsmbco]() ### AI overview A tutorial on setting up Compose Multiplatform previews for common code. It explains how to install the Kotlin Multiplatform IDE plugin, create a correctly configured project with the KMP wizard, and use previews in IntelliJ IDEA or Android Studio. An Android target is required. ### Source excerpt Compose Multiplatform now has support for previews in common code. Here's how you can get started with using them. ## Live Templates in Android Studio DevFeed: [Live Templates in Android Studio]() Original publisher: [Read original article]() Author: Segun Famisa Published: 2025-07-17T06:00:00Z Content type: tutorial Language: en Sources: [Segun Famisa]() Topics: [Android Studio](), [Kotlin](), [ide](), [IntelliJ IDEA](), [Code]() Tags: [android](), [android-studio](), [code](), [ide](), [intellij](), [jetbrains](), [keyboard](), [kotlin](), [shortcuts](), [tests](), [workflow]() ### AI overview This tutorial explains IntelliJ-based IDE live templates, with a focus on creating a custom Android Studio template for Kotlin test functions that use backticks. It describes the template settings, applicable context, abbreviation, description, and template variables. ### Source excerpt If you are already familiar with live templates, feel free to skip to the live template for kotlin tests If you use IntelliJ-based IDEs like Android Studio, WebStorm, etc., chances are that you have seen some kinds of "shortcuts" (pictured below) show up when you press some key combinations. These are called live templates. For example, if you type sout in a Java/Kotlin file, you see a pop-up like the one above. When you press tab, it autocompletes into System.out.println (in Java) or println in Kotlin. Live templates allow you to generate common code constructs by typing keywords that trigger the template. This feature is not new, and I definitely remember seeing it in the Netbeans IDE when I developed J2ME applications. If, like me, you write a lot of Android code in Android Studio, you may also know that if you type comp in a Kotlin file and press the tab key, a composable function is generated. I have personally found these templates extremely useful for developing faster, and I use them all the time. I even have a few of my own templates, and one of them is the main reason I am writing this article. -- Live Template for Kotlin tests One of the things I do almost every day when I write code is write tests. If you use Kotlin, you might know that backticks are allowed in test function names. I like to optimise my workflow, and I realised this was an opportunity to save myself a few keystrokes for every test I write. I ended up writing a live template to automatically create a test function with backticks (does anyone else find the backtick key awkwardly placed on the keyboard?). To set this up, I follow the instructions on JetBrains' website. You can do the same: CMD + , to open settings Navigate to Editor > Live Templates Select Kotlin group (the templates are usually grouped, but you can also create your own group if you so please) Click on the little + button or CMD + N , and select 1 or Live Template Now we can begin to set the details for the live template. Th ## Initial exploration of using Koog for developing Kotlin based AI agents DevFeed: [Initial exploration of using Koog for developing Kotlin based AI agents]() Original publisher: [Read original article]() Published: 2025-06-21T23:00:00Z Content type: tutorial Language: en Sources: [John O'Reilly]() Topics: [AI Agent](), [Kotlin](), [MCP](), [Model Context Protocol](), [Kotlin Multiplatform](), [Android Studio](), [Jetpack Compose](), [IntelliJ IDEA]() Tags: [ai-agents](), [android-studio](), [anthropic](), [compose](), [gemini](), [ide](), [kmp](), [kotlin](), [kotlin-multiplatform](), [mcp](), [mcp-server](), [ollama](), [openai](), [plugin](), [run-agent](), [tool]() ### AI overview This article explores Koog, a Kotlin-based framework for building and running AI agents. It demonstrates an agent using Google Gemini, MCP servers, climate-emissions data, and Compose UI code added to an Android Studio project, and discusses support for multiple LLM providers and custom tools. ### Source excerpt Koog, announced recently at KotlinConf, is a new Kotlin-based framework designed to build and run AI agents. This article will outline initial exploration of using Koog along with a number of configured MCP servers (specifically mcp-jetbrains which we'll use to control the IntelliJ/Android Studio IDE and also one based on the ClimateTraceKMP Kotlin Multiplatform (KMP) sample built using the Kotlin MCP SDK). ## My experience using Junie for the past few months DevFeed: [My experience using Junie for the past few months]() Original publisher: [Read original article]() Author: Julien Published: 2025-05-11T11:38:55Z Content type: opinion Language: en Sources: [Thoughts, stories and ideas.]() Topics: [junie](), [Artificial Intelligence](), [IntelliJ IDEA](), [coding]() Tags: [agent](), [ai](), [coding](), [development](), [experience](), [intellij](), [jetbrains](), [junie](), [kotlin]() ### AI overview A personal review of using JetBrains Junie over several months. The author describes Junie's Code and Ask modes, IntelliJ-based IDE integration, terminal command option, pricing, and distinctions from other JetBrains AI products. They value its IntelliJ integration, Kotlin support, and test-first focus, but criticize its slowness and limited ability to accept only part of a proposed solution. ### Source excerpt Junie is one of the best coding agent I've been trying out so far. Very well integrated with IntelliJ, great for Kotlin, and the test first focus makes it quite good at coming out with good results. However, I do miss the capability to only accept part of a solution and it can be very slowwwwww. [Next page]()