I'd like others' input on this: increasingly, I see Cursor, Jetbrains, etc. moving towards a model of having you manage many agents working on different tasks simultaneously. But in real, production codebases, I've found that even a single agent is faster at generating code than I am at evaluating its fitness and providing design guidance. Adding more agents working on different things would not speed anything up. But perhaps I am just much slower or a poorer multi-tasker than most. Do others find these features more useful?
Agentic Development Environment by JetBrains
11–20 of 65 posts
Re: Agentic Development Environment by JetBrains
#12Can't wait for this AI shit to be over so they can get back to their bread & butter...great dev tools.
Umm, it ain't ever gonna be over, it is a new era.
We need to adapt to new ways of thinking and ways of working with new tooling. It is a learning curve of sorts. What we want is to solve problems, the new tooling enables us to solve problems better by letting us free up our thinking by reducing blockers and toil tasks, giving us more time to think about higher level problems.
I remember this same sentiment towards AI when I was growing up, but towards cell phones...
Re: Agentic Development Environment by JetBrains
#13Ooof I forgot to cancel my jetbrains all products license when I switched to vs code. I better go do that now before it renews. Not because of AI but it also doesn’t help
Re: Agentic Development Environment by JetBrains
#14Not to be overly negative but I’m kinda disappointed with this and I have been a JetBrains shill for many years.
I already use this workflow myself, just multiple terminals with Claude on different directories. There’s like 100 of these “Claude with worktrees in parallel” UIs now, would have expected some of the common jetbrains value adds like some deep debugger integration or some fancy test runner view etc. The only one I see called out is Local History and I don’t see any fancy diff or find in files deep integration to diff or search between the agent work trees and I don’t see the jetbrains commit, shelf, etc. git integration that we like.
I do like the cursor-like highlight and add to context thing and the kanban board sort of view of the agent statuses, but this is nothing new. I would have expected at the least that jetbrains would provide some fancier UI that lets you select which directories or scopes should be auto approved for edit or other fancy fine grained auto-approve permissions for the agent.
In summary it looks like just another parallel Claude UI rather than a Jetbrains take on it. It also seems like it’s a separate IDE rather than built on the IntelliJ platform so they probably won’t turn it into a plugin in the future either.
Re: Agentic Development Environment by JetBrains
#15Can't wait for this AI shit to be over so they can get back to their bread & butter...great dev tools.
Umm, it ain't ever gonna be over, it is a new era. We need to adapt to new ways of thinking and ways of working with new tooling. It is a learning curve of sorts. What we want is to solve problems, the new tooling enables us to solve problems better by letting us free up our thinking by reducing blockers and toil tasks, giving us more time to think about higher level problems. I remember this same sentiment towards A…
> What we want is to solve problems
speak for yourself, i want to understand everything and be elbow deep in the code
Re: Agentic Development Environment by JetBrains
#16Seems this is the product JetBrains mentioned in their sun-setting announcement of the short-lived CodeCanvas product.
https://blog.jetbrains.com/codecanvas/2025/10/jetbrains-is-s...
Re: Agentic Development Environment by JetBrains
#17I really like this initiative, I think the biggest value here isn't the multiple sessions or worktrees, but an interoperable protocol between these coding agents through a new UX. A sort of parent process orchestrator of the many agents is something I want, is there other tools that do that today? e.g. run Claude, Codex, Gemini, all together and sharing data with one another?
Re: Agentic Development Environment by JetBrains
#18Can't wait for this AI shit to be over so they can get back to their bread & butter...great dev tools.
Umm, it ain't ever gonna be over, it is a new era. We need to adapt to new ways of thinking and ways of working with new tooling. It is a learning curve of sorts. What we want is to solve problems, the new tooling enables us to solve problems better by letting us free up our thinking by reducing blockers and toil tasks, giving us more time to think about higher level problems. I remember this same sentiment towards A…
bookmarking this to laugh at it in 2030
Re: Agentic Development Environment by JetBrains
#19Earlier quoted context omitted.
Umm, it ain't ever gonna be over, it is a new era. We need to adapt to new ways of thinking and ways of working with new tooling. It is a learning curve of sorts. What we want is to solve problems, the new tooling enables us to solve problems better by letting us free up our thinking by reducing blockers and toil tasks, giving us more time to think about higher level problems. I remember this same sentiment towards A…
> What we want is to solve problems speak for yourself, i want to understand everything and be elbow deep in the code
I will empathize with you there. I totally want to understand everything too. I LOVE being elbow deep in code for hours on end, especially late nights, so, much, FUN!!!
It is just now, I don't have to do that to actually build something meaningful, my ability to build is increased by some factor, and it is only increasing.
And coding LLM's have become a great teacher for me, and I learn much faster, for when I do want to dig deeper into the code, I can ask very nuanced questions about what certain code is doing, or how it works and it does a fairly good job of explaining it. Similar to how a real person would if I were in meat space at an office. Which I don't get that opportunity anymore in this remote life.
Re: Agentic Development Environment by JetBrains
#20I'd like others' input on this: increasingly, I see Cursor, Jetbrains, etc. moving towards a model of having you manage many agents working on different tasks simultaneously. But in real, production codebases, I've found that even a single agent is faster at generating code than I am at evaluating its fitness and providing design guidance. Adding more agents working on different things would not speed anything up. Bu…
My context window is small. It's hard enough keeping track of one timeline, I just don't see the appeal in running multiple agents. I can't really keep up.