Why is the AI conversation feature incomplete after Void is compiled and built into a Windows installation package?

[cuccshpere]

Question: Why is the AI conversation feature incomplete after Void is compiled and built into a Windows installation package?

Background: A custom enterprise model has been integrated, and it is confirmed that both the integration functionality and the model's functionality are working correctly.

Description of Screenshots:

The first two screenshots show the interface after entering [@] and clicking [files].

The last two screenshots show the interface after clicking [folders].

Issue Details:

In the first two screenshots, although files are displayed after clicking [files], they are all configuration files. The .java files from the corresponding project are not shown, which is strange. Could this be an issue with the search algorithm?

In the last two screenshots, the result is "No results found." However, I actually have a code project open in Void dev, and I have opened several .java files from that project in the main editor window.

[andrewpareles]

The files/folders dropdown relies on VSCode's internal file search mechanism, so sometimes the issue resolves itself when you press cmd+shift+F (internally, this initializes the search service).

If that doesn't resolve it, let me know how you're building Void - this might be an OS-specific storage issue. There are some encryption, storage, and keychain aspects of building on each OS that we're delegating to our build pipeline, a fork of VSCodium.

[cuccshpere]

The files/folders dropdown relies on VSCode's internal file search mechanism, so sometimes the issue resolves itself when you press cmd+shift+F (internally, this initializes the search service).

If that doesn't resolve it, let me know how you're building Void - this might be an OS-specific storage issue. There are some encryption, storage, and keychain aspects of building on each OS that we're delegating to our build pipeline, a fork of VSCodium.

---

Okay, here's what I did. I followed these steps exactly:

1. First, I completely deleted the node_modules folder using the command Remove-Item node_modules -Recurse -Force (I'm on Windows).
2. Then, I cleared the npm cache with npm cache clean --force.
3. After that, I ran npm install.
4. Next, I executed npm run compile.
5. Finally, I launched Void-dev by running ./scripts/code.bat.

But after all that, I'm still seeing the same issue I mentioned before. Here's the specific behavior:

• When I type @, the menu appears as it should, with both [files] and [folders].
• Clicking on [files] works perfectly. It displays the file list, and I can see the corresponding logs in the Developer Tools Console.
• The problem is when I click [folders]. The UI just says "No results found". What's strange is that the logs in the console are identical to the ones from when I clicked [files]. It really seems like the function to fetch the folders isn't even being called.

[andrewpareles]

Interesting, sorry about this - will investigate.