We swapped our IDEs for ADEs: what does it change for us developers?
Ten AI chat windows open, and the IDE can't keep up. They switched to ADEs. Alexandre and Xavier share their verdict.
1, 2, 3... 5, 10, 15: can you still find your way around all the AI chat windows open on your screen right now? How do you parallelise your sessions while avoiding code or execution conflicts? Do IDEs still match the way you work?
Faced with these problems, a new category of tools has emerged in recent months: Agentic Development Environments. And today, it's no longer a JS framework but a new ADE that ships every week. So here's a field report on what changes when you drop your favourite IDE to switch to the world of ADEs.
Beyond worktrees, we'll see what it really means to orchestrate agentic sessions in parallel. We'll break down the concepts and features of these ADEs, exploring how they fit your new way of working with AI, and what room is ultimately left for our good old IDEs.
You'll leave with cool tools to try, automation ideas to set up in your daily dev routine, and a concrete picture of what tomorrow's development experience looks like.
