Hey there. I'd come across aider a few weeks ago - thrilled to have your input on this.
You're correct that Voxos in its current form does not directly work with the user's file system. I'll admit I chose my words carefully in saying that it spares you from copy and pasting between ChatGPT and your IDE - not necessarily that you won't be copy and pasting any more. I feel like having the text response dump to a text editor helps me speed up my workflow considerably when contrasted with the ChatGPT UI being "read-only" in this sense.
Anyways, I'd been messing around with function calling in an earlier version of Voxos and plan on bringing all that work into this beta soon. In terms of my approach, I plan on using docker to host a network mapped drive on the host machine. Then connecting the IDE from the host to the network mapped drive. I'm not sure how well that will carry over to the non-beta version of Voxos that I envision will come with an installer for non-technical users. I haven't put that much work into the idea yet.
An alternative was to host all of it in the cloud and simply offer a web IDE to a container, then make sure there's reliable backup and revert system in place if/when things go south. That's heading more towardsa hosted solution though and I simply don't have time to support paying customers even once Voxos matures to the point I'd liked for a v1.0.
I'll take a closer look at the unified-diffs when I get a chance!
You're correct that Voxos in its current form does not directly work with the user's file system. I'll admit I chose my words carefully in saying that it spares you from copy and pasting between ChatGPT and your IDE - not necessarily that you won't be copy and pasting any more. I feel like having the text response dump to a text editor helps me speed up my workflow considerably when contrasted with the ChatGPT UI being "read-only" in this sense.
Anyways, I'd been messing around with function calling in an earlier version of Voxos and plan on bringing all that work into this beta soon. In terms of my approach, I plan on using docker to host a network mapped drive on the host machine. Then connecting the IDE from the host to the network mapped drive. I'm not sure how well that will carry over to the non-beta version of Voxos that I envision will come with an installer for non-technical users. I haven't put that much work into the idea yet.
An alternative was to host all of it in the cloud and simply offer a web IDE to a container, then make sure there's reliable backup and revert system in place if/when things go south. That's heading more towardsa hosted solution though and I simply don't have time to support paying customers even once Voxos matures to the point I'd liked for a v1.0.
I'll take a closer look at the unified-diffs when I get a chance!