WASI sandbox
The proxy runs wasm32-wasip1 in isolation. A plugin that hangs is cut short; the editor and the other plugins keep going.
Extensibility
Make it yours.
Then make it more.
A plugin is a WASI module. The proxy runs it in a sandbox, held to the permissions in its volt.toml. Most start a language server; the editor does the rest.
Writing a plugin →HOSTGraphoOS
- Native editor
- LSP traffic
- Diagnostics
WASIplugin.wasm
- wasm32-wasip1
- named processes
- allowed hosts
rust-analyzergoplsyours
In the registry
Eleven plugins.
The sandbox stays.
Rustrust-analyzer · v0.3.3050
Pythonpyright · v0.2.0
Gogopls · v0.1.0
C / C++clangd · v0.1.1
TypeScripttypescript-language-server · v0.2.0
HTMLhtml-language-server · v0.1.0
CSScss-language-server · v0.1.0
JSONjson-language-server · v0.2.0
YAMLyaml-language-server · v0.2.1
TOMLtaplo · v0.1.0
Markdownmarksman · v0.1.0
volt.toml
What is not written
is refused.
api = "1.2"
name = "graphoos-rust"
[permissions]
processes = ["rust-analyzer", "codelldb", "which"]
network = ["github.com", "*.githubusercontent.com"]Language server
The plugin says how to start the LSP. GraphoOS does the traffic, the diagnostics, the symbols and the completions.
Permissions in volt.toml
processes and network by name. Anything not written there is refused.
Open by design
Nothing hidden
behind the surface.
The host speaks Plugin API 1.2. The guest is wasm32-wasip1. Anything not in volt.toml is refused.