Curious about your reverse engineering efforts - hat was the trickiest part about getting Firebender’s background agents to run in fully isolated workspaces in Jetbrains IDEs? Did you run into issues with IntelliJ’s project management / sandboxes behind the scenes, especially when trying to keep the agent’s changes cleanly separated from your main code? How did you manage those edge cases or unexpected side effects
Really interesting launch, there’s lots like this to do in order to improve devex in the Jetbrains ecosystem
Curious about your reverse engineering efforts - hat was the trickiest part about getting Firebender’s background agents to run in fully isolated workspaces in Jetbrains IDEs? Did you run into issues with IntelliJ’s project management / sandboxes behind the scenes, especially when trying to keep the agent’s changes cleanly separated from your main code? How did you manage those edge cases or unexpected side effects
Really interesting launch, there’s lots like this to do in order to improve devex in the Jetbrains ecosystem
Building the "chrome tab" style experience for background agents was insanely tricky.
We have to open IDE project tabs without losing focus on the primary project which is impossible to do with the interface Jetbrains offers.
We reverse-engineered IntelliJ's project tab implementation and hacked our own version by calling internal IDE functions directly with reflection.
This was all to literally just open a tab in the IDE without losing focus, but it feels 10x better and is all worth it for our users.