after 48 hours, using the most productive stack in the wolrd: php, @laravel, @phpstorm & @getsome_air, we are proud to introduce: https://t.co/Afj2hcC5YH
social network for developers; sign-in with @github, done!
An agent writes the code now. Do you still need an IDE?
You do if you want to understand and verify what the agent did.
🎥 In our new video, we talk about the role of an IDE now that humans aren't the only ones working on the code. https://t.co/Fd7YyX43EV
Will we still have a job in five years? On Nov 13, JetBrains AI.js Day puts frontend's scariest AI questions on air, live, online, and free.
Kent C. Dodds, Marina Wyss, Danny Thompson, and more.
Register now: https://t.co/P8cjO12cDg
wild 48 hours. still processing it tbh
so many marketing takeaways from this @jetbrains x nunonation event. will write them up properly on monday
we went viral (hacker news, x, etc) using a format most marketing teams wouldn't touch, precisely because it's so uncomfortable: raw, unfiltered, no script, just us
people don't fall in love with a brand. they fall in love with the humans behind it
thank you to everyone who shared, posted, dm'd, roasted us, all of it. means a lot
huge thanks to @brendt_gd, @matthieunapoli and @vanamerongen for being exceptionally awesome
The fix for WI-33248 covers one case: a package from a Composer path repository with symlink: true is no longer added to the include paths as vendor/<vendor>/<pkg>. PhpStorm indexes the package once, from its real directory. The fix needs no setup.
Since 2026.1 PhpStorm excludes only some Symfony cache directories in the project, such as var/cache and var/sessions by default, not the whole var/ directory.
To stop the indexing, the var/ directory should be marked as excluded. If PhpStorm still indexes it after that, open Settings > PHP > Include Path and review the list there. An include path entry overrides the exclusion.
If that does not help, please file a new issue at https://t.co/7diaH0ucdG and share more details about your setup, composer.json content, etc.
Staying on top of the PHP ecosystem just got easier 👇
PhpStorm is proud to sponsor @PHPNewsnet to bring you the latest releases, RFCs, and community news every day!
Check out today's updates: https://t.co/2IISKoGKkB
We connected IntelliJ IDEA’s code intelligence to Claude Code and Codex, then tested the setup with Netflix.
The first public results are out.
Typical efficiency gains: 20–30%.
Best code-navigation case: ~65%.
These results come from two real codebases. The efficiency metric averages token savings and time savings.
Correctness stayed stable or improved.
Here’s what we actually built.
The code engine behind IntelliJ IDEA ran headlessly, giving agents access to its capabilities through a CLI backed by a daemon.
LSP alone wasn’t sufficient.
Agents needed a convenient way to invoke the tools. The backend also needed to stay running and keep the project index warm between calls.
The idea is straightforward.
An IDE has already mapped the structure of your code and its dependencies — including what’s inside compiled libraries.
An agent can use that knowledge instead of spending time and tokens reconstructing it.
But the most interesting finding was which models benefited most.
The strongest models saw the biggest gains.
Especially at higher reasoning effort.
In these experiments, more capable models were also better at taking advantage of code intelligence.
My takeaway: better models and better tools aren’t competing bets.
You don’t have to choose between investing in model intelligence and giving agents better access to your codebase.
The two can reinforce each other.
Huge thanks to @pbakker and the Netflix team for working with us on this!
me, @brendt_gd and @matthieunapoli are building the best social network for developers ever made
live this thursday from the jetbrains office, using @getsome_air
everyone says AI makes you 100x faster. we'll find out on camera
https://t.co/XiCbn4ie2z
Better yet, try it yourself. The fastest way to get your hands on Air:
1. Download PhpStorm 26.3 EAP: https://t.co/u2O17POGdF
2. Look for the Air icon or press ⌘2 (Ctrl+2).
Holy moly, we’ve seen a lot of interest in JetBrains Air since the announcement!
-Air in IDEs: for developers
-Air Teams: for team leads & engineering managers
-Air Governance: for CTOs & engineering directors
Here’s how to try these things:
Links below 🧵
A full social network. Built in PHP. In 48 hours.
@enunomaduro, @brendt_gd, and @matthieunapoli go live from the JetBrains office on October 15th and 16th.