WEEP
Pre-release · v0.1.0 · build from source
Fleet's shape, native.
WEEP is a code editor written in Rust on GPUI, built to look and behave like JetBrains Fleet: the islands layout, the Files, Search, Git, Terminal and Run tools, Fleet's own theme and keymap files loaded unchanged, and every size and colour measured off a running copy. No JVM, no account, no telemetry. It is an independent project, not affiliated with JetBrains.
Version 0.1.0, free software under the MIT license. There are no release builds yet:
WEEP is built with cargo on Linux, Windows and macOS —
see where it is.
Fleet is the reference
"Looks like Fleet" is measured, not felt. Fleet is run beside WEEP, the same scene is played into both, and the screenshots are compared edge by edge. A milestone is not finished until its scenes agree to within one logical pixel and every colour is the theme's exact value.
Every constant has a source
Island gaps, tab heights, row pitches and type sizes live in one table in the code, and each value is recorded with where it came from — a probe screenshot, one of Fleet's own files — or marked as still an estimate.
Fleet's formats are WEEP's
Themes, keymaps and settings.json use Fleet's keys and action ids
verbatim, so a Fleet theme or keymap loads unchanged, and WEEP falls back to Fleet's
own settings file so an existing setup carries over.
Nothing from the binary
No code and no assets come out of the Fleet distribution beyond the openly licensed fonts. Icons are JetBrains' Apache-licensed expui set or WEEP's own drawings.
settings.json keys readWhat is in it today
WEEP clones Fleet as it behaves without Smart Mode first, then adds Smart Mode through language servers instead of Fleet's IntelliJ backend. Milestones M0 to M6 are built; M7, Smart Mode over LSP, has its first pass in.
Everything Fleet does to text
Multiple carets, find and replace, folding and sticky lines, expand and shrink
selection, soft wrap, the indenter and auto-pairs, .editorconfig, autosave,
and one document shared by every tab and split that shows it. Highlighting is
tree-sitter, mapped onto Fleet's textAttributes keys.
Goto, Search, Files, Settings
The Goto popup with its preview, Text Search and replace across the workspace, a Files
tree with multi-select and drag and drop, Fleet's menus, dialogs and notifications, and
the Settings pages as an editor tab that writes your settings.json.
The tools around the code
Status in the tree and the gutter, staging and commit, history, blame, a side-by-side
Changed Files tab, push and pull; a terminal on a real PTY with Fleet's profiles; and
.fleet/run.json configurations with their output and problems.
Language servers, Fleet's surface
The lightning, diagnostics, semantic highlighting, completion, parameter info, documentation, go to declaration, find usages, rename, quick fixes and reformat — through rust-analyzer, which is what Fleet's Rust Smart Mode runs too. The debugger over DAP comes next.
Native, and nothing else
WEEP is a single Rust binary drawing with the GPU through GPUI, the toolkit from Zed. The text model, the highlighter, git, search, the terminal and the language-server client are separate crates that know nothing of the interface, and each is tested on its own.
No account, no network of its own
There is nothing to sign in to and nothing phones home: no telemetry, no update check, no license call. The only processes WEEP talks to are the ones you run — git, your shell, your language server.
Kept short on purpose
tree-sitter instead of TextMate grammars, LSP and DAP instead of the IntelliJ backend, a natively painted Markdown preview instead of an embedded Chromium. Everything not on that list follows Fleet.
What WEEP will not be
Collaboration, remote workspaces, the JetBrains account and AI are not planned. Vim mode, Docker, SSH and WSL workspaces are "later or never".
Where it is, plainly
WEEP is v0.1.0 and has no release builds yet. It edits real files in place and saves them, autosave included; keep your work in version control while you try it. Many sizes on the newest surfaces are still estimates until their probe scenes run against Fleet.
Linux, Windows, macOS
WEEP builds and runs on all three with a stable Rust toolchain. On Windows it draws Fleet's own caption; elsewhere it keeps the desktop's title bar, as Fleet does.
Rust, JSON, TOML, Markdown
Those four have tree-sitter grammars today, and Smart Mode attaches rust-analyzer. Other files open as plain text with the full editor around them.
Known gaps
No debugger, no inlay hints or code vision, no inline rename, no snippets, and no language servers beyond rust-analyzer.