voideditor
Void agent disabled (error when opening Void agent settings and no onboarding launched) when running IDE with "void-server" (reh-web)
For example, "./void-server --without-connection-token --host 0.0.0.0" .
One can access the Void IDE remotely with a web browser, but if we try to open the Void Settings (the settings populated by the on-boarding helper) - then we get this:
The editor could not be opened due to an unexpected error. Please consult the log for more details.
The logs show:
File not found: /home/worker/void/reh-web/node_modules/vsda/rust/web/vsda_bg.wasm
File not found: /home/worker/void/reh-web/node_modules/vsda/rust/web/vsda.js
The browser-based IDE can open the core vscode settings, but not the Void-specific settings where we would configure our inference providers (like setting the local Ollama URL) to be used by the Void Agent.
If the remote code-server extensions are proprietary to the "official" MS VSCode release, then being able to use Void's IDE-integrated coding agent via the void-reh-web server is super useful . It a practical way to run Void on the remote machine where the build/dev/repo resources are - without having to rely on X11 for the desktop app interface. This would also give us the gitpod-like ability to bundle Void in a container for a project with complex tooling/build/data requirements.
We're not focused on the reh-web part of the project right now, but thanks for reporting - you're not the first to want to use Void in the browser!
Is there any chance any of the reh files here are useful to you? https://github.com/voideditor/binaries/releases
We're not focused on the reh-web part of the project right now, but thanks for reporting - you're not the first to want to use Void in the browser!
Is there any chance any of the reh files here are useful to you? https://github.com/voideditor/binaries/releases
@andrewpareles : The release binaries (expanded assets) are where i downloaded the package containing the void-server.
I can run the browser-based void editor that way - but the onboarding sequence (of configurator screens to set up the agent (like pointing it to a local ollama-serve listener)) doesn't show up. Happy to help dig and create a PR if you'd like!