Why GraphoOS ​

Most code editors today are web applications wearing a desktop frame. They start slowly, they keep a JavaScript runtime between you and every keystroke, and the more you install the heavier they get. GraphoOS exists because Empoorio needed an editor that behaves like a native tool: it opens instantly, it stays out of the way, and it keeps the code and the environment in the hands of the person using it.

Principles ​

Native, from the rope up. GraphoOS is written in Rust. Buffers are ropes, so a 100 MB file edits like a 100-line one. The UI is drawn on the GPU by Floem, a reactive toolkit built for this editor, not a browser engine.

Local editing, remote everything else. The editor is split in three: the UI, which owns the buffer and every keystroke; the proxy, which talks to the file system, language servers and plugins; and the plugins themselves. When you develop on a remote machine only the proxy and the plugins move there, so typing never waits on the network.

Configurable, not scriptable by accident. Themes, icons, keymaps and settings are plain TOML files. Plugins are WASI modules: sandboxed, portable, written in any language that compiles to WebAssembly.

Transparent assistance. Where GraphoOS integrates models and agents, they run with explicit permissions, visible costs and reviewable diffs, and they work with local models first. The editor helps; it does not take over.

Open. GraphoOS is Apache-2.0 and developed in the open at github.com/Empoorio/graphoos, alongside the rest of the Empoorio ecosystem.

Source: docs/why-graphoos.md