Q Can you spell out what you couldn't do in VS code? Because I think when we did the, the cursor episode explain, then everybody on agronews is like, oh, why, why did you fork? Why you could have done it in an extension? Like, can you maybe just explain more of those limitations?
A I mean, I think a lot of the limitations around, like, APIs are pretty well documented. I don't know if we need to go, necessarily go down that rabbit hole. I think it was when we started thinking, okay, what are the pieces that we actually need to give the AI to get to that kind of, you know, emergent behavior that Bruin talked about, right? And, and yes, we were talking about all the knowledge retrieval systems that we've been building for the enterprise all this time. Like, that's obviously a component of that. You know, we were talking about all the different tools that we could give it access to so they can go, like, do that kind of terminal execution and things like that. Then the third main category that we realized would be like kind of that magical thing where you're not out there writing out a PRD, you're not scoping the problem for the AI, is that if we're actually being able to understand the kind of the trajectory of what developers are doing within the editor, right, if we actually be able to see like, oh, the developer just went and opened up this part of the directory and tried to view it, then they made these kind of edits, and they tried to do like some kind of commands in the terminal, and if we actually understand that trajectory, then our ability for the AI to just be immediately be like, Oh, I understand your intent. This is what you want to do without you…
AI assessment note: “limitations around, like, APIs are pretty well documented. I don't know if we need”