{"id":577044,"date":"2025-06-23T10:20:03","date_gmt":"2025-06-23T09:20:03","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=phpstorm&p=577044"},"modified":"2025-06-26T17:39:23","modified_gmt":"2025-06-26T16:39:23","slug":"discover-junie-for-phpstorm","status":"publish","type":"phpstorm","link":"https:\/\/blog.jetbrains.com\/fr\/phpstorm\/2025\/06\/discover-junie-for-phpstorm","title":{"rendered":"Discover Junie for PhpStorm: A Game-Changing AI Coding Agent for PHP Development"},"content":{"rendered":"\n

With the release of Junie<\/a>, the AI coding agent by JetBrains, PhpStorm<\/a> has entered the realm of agentic IDEs. Now, the PhpStorm IDE doesn\u2019t just provide classical developer productivity tools and AI assistance features, but can also do massive amounts of work for PHP developers autonomously.<\/p>\n\n\n\n

Unlike other coding agent plugins, Junie is native to PhpStorm, which means it uses PhpStorm\u2019s core features, such as source code navigation, project structure navigation, Search Everywhere<\/em>, and code inspections to plan and execute multistep tasks and supervise the outcome. <\/p>\n\n\n\n

You can install<\/a> Junie like any other PhpStorm plugin and open it in the IDE by clicking the <\/em><\/strong>Junie<\/em> icon on the right-hand sidebar.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In this blog post, we\u2019ll follow Junie doing its work and see how it fits into your familiar PhpStorm workflow, while kicking off a whole new way of writing code.<\/p>\n\n\n\n

Starting with a clean Laravel project <\/h2>\n\n\n\n

Let\u2019s start with a clean Laravel project. There\u2019s nothing here but the defaults, and what I want to do is add some functionality to it. So my prompt is:<\/p>\n\n\n\n

Implement CRUD actions to manage books via web forms, also create and run a seeder to add 10 books into the database, write tests, and execute them. Use the Tailwind CSS form component library.<\/code><\/p>\n\n\n\n

?Tip: <\/strong>To avoid follow-up clarifications where possible, provide Junie with detailed guidelines and instructions in the initial prompt. This helps minimize the number of requests sent to LLMs and optimize the token usage, which means you\u2019re left with a higher JetBrains AI quota<\/a>!<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Watching Junie work<\/h2>\n\n\n\n

When I run the prompt, Junie starts by creating a plan and then follows the proposed plan step by step, stopping at terminal commands for user confirmation.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

As you can see, Junie is pretty transparent with what it does and which files it searches for, opens, or edits, reporting on what exactly is being performed at each step along the way. <\/p>\n\n\n\n

While Junie is running, you can open Junie\u2019s terminal<\/strong> to see the CLI command currently executed by the agent and the complete output history. You can even interact with the terminal while Junie is running some of the commands.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

When Junie is done, you can double-click the changed or added file to open it in PhpStorm\u2019s diff viewer, locate and open the file itself in the editor, or roll back changes for the edited files. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

From here, you can accept all changes, give Junie a follow-up task, or roll everything back if needed.<\/p>\n\n\n\n

In our case, Junie created CRUD screens for managing books. It also wrote tests and executed them without any manual interference. There\u2019s a new database seeder, and it was actually run, with 10 test books added to the database. <\/p>\n\n\n\n

Exactly as instructed! <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n
\n
\n Try Junie<\/a>\n <\/div>\n <\/div>\n\n\n\n\n\n\n\n

The power of Junie guidelines<\/h2>\n\n\n\n

In the initial prompt, I instructed Junie on which technologies to use. However, for more consistent outcomes, it\u2019d be better to create a .junie\/guidelines.md<\/code> file in the project root and list all the preferred technologies, naming conventions, and coding standards there. Guidelines can also spare Junie from making irrelevant assumptions and minimize follow-ups or manual intervention.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

You can compose the guidelines file yourself, ask Junie to generate project-specific guidelines on an existing project for you, or reuse the guidelines and rules that are specific to your framework or technology stack shared by other developers, for example, Laravel guidelines by David Carr<\/a>. <\/p>\n\n\n\n

?Tip: <\/strong>Use the .aiignore<\/code> file to restrict Junie from accessing specific files and directories. The .aiignore<\/code> file follows the same syntax and pattern format<\/a> as the .gitignore<\/code> file.<\/p>\n\n\n\n

Allowed terminal commands<\/h2>\n\n\n\n

Additionally, in the example above, I manually confirmed all terminal commands run by Junie. However, I feel confident in allowing Junie to run any php artisan<\/code> command without confirmation. To do so, I\u2019ll add this type of command to the Junie allowlist in the IDE settings via Settings | Tools | Junie | Action Allowlist<\/em> using the RegEx syntax.<\/p>\n\n\n\n

Allowing all php artisan<\/code> commands, including with complex arguments and options, would look as follows:<\/p>\n\n\n\n

^\\Qphp artisan \\E\\S+(?:\\s+(?:[-\\w:=]+|\"[^\"]*\"|'[^']*'))*$<\/code><\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

To enable Junie to run all terminal commands without user confirmation, select the Brave Mode<\/em> checkbox.<\/p>\n\n\n\n

Ask mode<\/h2>\n\n\n\n

Junie comes with the agentic code mode selected by default. However, you can also chat with Junie in Ask<\/em> mode, asking questions referencing your project context but without having your code changed. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Using Junie on existing projects<\/h2>\n\n\n\n

We started with a clean project and let Junie do its thing. But what about existing projects? Junie is optimized for a profound understanding of the project context and working with large-scale repos and complicated tasks. PHP developers can use Junie to:<\/p>\n\n\n\n