# junie Junie is an AI coding agent by JetBrains that runs in terminals, JetBrains IDEs, GitHub, and GitLab to perform software development tasks. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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. ## 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. ## Does Junie Create Accessible Android Apps? DevFeed: [Does Junie Create Accessible Android Apps?]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2025-06-10T04:54:16.242000Z Content type: opinion Language: en Sources: [Eevis Blog]() Topics: [junie](), [Accessibility](), [Artificial Intelligence](), [Android](), [Testing](), [IntelliJ IDEA]() Tags: [accessibility-testing](), [ai](), [android](), [android-studio](), [junie]() ### AI overview The article reports on two rounds of testing Junie, JetBrains' coding agent, by generating Android apps and evaluating their accessibility. It also discusses Junie's structured workflow, unnecessary library additions, a KSP version issue, and differences between its Early Access and generally available versions. ### Source excerpt I'm continuing my tests with AI-generated Android code and how accessible these generated apps are. This time, the tool of choice is Junie, the coding agent by JetBrains. If you want to know why I'm doing this or want to read my take on how accessible code Gemini creates, the first post is available at Does Gemini Create Accessible Android Apps?. So, I got into the Early Access Program (EAP) before Junie was generally available and generated the first app. I had all these plans to proceed to the second run and write this blog post sooner, but then life happened, and I founded my own company. Suddenly, time passed, and Junie is now generally available. Before we dive into the application generation and accessibility testing, I'll share a couple of words about Junie I wrote right after the first try, with some additions after the second run. Junie As mentioned, I got access to EAP and was curious to try Junie out, as it differed from the AI solutions for coding I'd used before. Particularly, it also changed the files and didn't just give me the code, and I could skip all the hard work of creating files and copy-pasting the code into those files. Some thoughts I had: I was impressed by the structured approach for doing things. It was easy to follow what was happening next and what was coming after that. When creating the first app, Junie kind of went overboard with adding libraries like Room into the project, but not using them in the code. With the first app, I had to solve one KSP version issue by hand, because I got tired of Junie trying to find a working library version. It used some non-existent version numbers first. The second app used kapt, which resolved the version right away. I had to iterate a bit with the first version to get all the features I wanted, like adding yarn. The second app generation was smooth from this point of view. The App As with the tests with Gemini, I did two rounds of testing - first, with the Early Access Program version back at the b ## Vibecoding a Totoro tribute with Junie DevFeed: [Vibecoding a Totoro tribute with Junie]() Original publisher: [Read original article]() Published: 2025-03-02T21:02:23Z Content type: tutorial Language: en Sources: [maiatoday]() Topics: [junie](), [Compose](), [Kotlin Multiplatform](), [Canvas](), [shaders]() Tags: [animate](), [canvas](), [code](), [compose](), [junie](), [kotlin](), [kotlin-multiplatform](), [screen](), [shaders]() ### AI overview The article describes using Junie to experiment with visual drawing techniques in a Kotlin Multiplatform Compose desktop project. The project combines canvases, gradients, paths, shapes, text, shaders, animations, and interaction to create a Totoro tribute, without aiming for production readiness. ### Source excerpt Sunday afternoon. Perfect time to hang out with Junie. I want to refresh my memory on some Compose drawing techniques. I am not really in the mood for Googling. I don't need a production ready app. I really just want to mess around. How far can I vibe code this. I'll start off by setting Junie to brave mode. I added an image and some colours to the repo of a blank compose desktop project. I also put a copy of an older blogpost of mine with some drawing techniques. I set some ground rules with the first prompt and then just keep asking Junie to add things. Create a guidelines file with the following information and update the README.md file. Let's explore some visual techniques in this Kotlin multiplatform project. The aim is to go for variety of techniques. Feel free to use the canvas, brush, paint, gradient, lines, paths, rounded polygons, skia shaders, text, colours, shapes. Or anything that will create an interesting visual effect. Animations are not necessary but can be added. The project does not have a practical application other than to demonstrate how to create interesting visual elements and to have some fun. It is a visual tribute to the Studio Ghibli film, [My Neighbor Totoro](https://en.wikipedia.org/wiki/My_Neighbor_Totoro). * It does not need any tests * Layer all the visual techniques on the main composable screen. * Find the suggested fonts in the resources folder * Find inspiration in the docs/looks folder and in the docs/blogpost folder I think Junie got what I wanted to do, I never explained what Totoro looks like but it figured out something from the included inspiration image. The early experiments needed some tweaking The only time the project didn't run was when Junie didn't download the new fonts but I found the instructions on where to get the fonts added to the README.md. I had no real expectations so I'm pretty happy with the final result. Animating rain and clickable wobbling Totoro. No explanations really what can I say I didn't read the