Repository navigation
Releases
Release v0.1.0
The first release of liquify, the native IDE for repositories kept in liquid. It is experimental: an early preview to try liquid's editing model, not a tool for daily work. Release epic: #154.
It builds against liquid 27d56ba3726f19834dce23125e0e15299f889ba7 (libliquid 0.2.0); see store compatibility. There is no signed installer: build from source, as the README says.
What it includes
As a first release, this lists everything liquify does. The command list is generated from the code in docs/ui/commands.md (94 commands); the command line is liquify --help.
Front door and repositories
- Open a local folder, create a repository, clone one from a lake, reopen one of eight recent repositories, show this computer's signing identity, and open more windows.
- Repositories open off the render thread; switching repositories needs no restart. An unreadable repository and an unreachable lake each have their own retry state, and a failed clone names its cause (offline, TLS, token, access, not found, busy, unsupported).
- Unsaved buffers are protected by Save / Discard / Cancel on close, on switching repository and on quit.
Editor
- A retained GPU text layer inside the shell: multi-cursor and column edits, search and replace in a buffer and across the repository, folds, soft wrap, bracket matching, liquid syntax, and per-buffer undo and redo.
- Gutters for lines, diagnostics, attribution, presence and drive state.
- A standard non-modal input mode and a modal command/insert mode.
- Save writes a signed drip through libliquid. Cut Change names the drips saved since the last change as one change, after showing what it gathers.
- Repository operation history.
Navigation and C/C++ analysis
- Quick Open and Symbol Search, keyboard-first (Up, Down, Enter, Escape); definitions, references, call relationships, breadcrumbs, recent locations, back and forward.
- Repository tree actions: open, rename, move, new file, reveal.
- C and C++ analysis from liquid's graph: closed-file stubs, error-tolerant trees for open files, hover, completion, and build diagnostics inline and in a panel.
- Structural edits: syntax-node selection, cross-file rename and extract function, previewed, then applied as one drip per changed file and one liquid operation. The headless
--apply-editscommand takes the same records.
Lake
- Push (F9) to the lake a repository came from or to its sync remote; Set Lake when there is neither.
- Request Review, and the Review panel: changes pulled through liquid, inline hunks and conflict values, comments anchored at the cursor that follow revised heads, and review state.
Build and test
- F7 builds and F8 runs tests through liquid's per-checkout daemon, with the action stream, critical path and scheduling choices. With no recorded build, F7 offers Set Up Build, which proposes a command and records it.
- Failed actions show their diagnostics on the affected lines.
Shell
- One panel registry: every panel docks, floats, tabs and re-docks, and the layout is kept per repository and can be reset.
- One command registry is the only key path: window keys, the command palette and the native macOS menus run the same commands, and a rebind in Settings reaches all three at once. Two commands claiming one key run neither, and both are named.
- Searchable settings from user and repository
.liquidfiles: theme, fonts, editor behavior, keymaps, the assistant, lake accounts, and telemetry (off by default). Credential values never enter the settings model. - Light and dark themes from the Orama design tokens and IBM Plex, controls that follow lake's kit, and a status bar that reports build, sync, hydration and the daemon's true state.
- CJK input methods and dead keys, rich and plain clipboard, file drops, keyboard traversal with visible focus, macOS accessibility labels, high contrast, and the system's reduced-motion setting.
Plugins
- Native plugins on liquid's versioned frontend C boundary register graph queries, commands and data-only panels.
- Each dynamic plugin runs in its own sandboxed host process (macOS sandbox, Linux Landlock and seccomp, Windows low integrity). A crash or hang fails only its own call, and a plugin is disabled after three restarts.
- Calls to plugins are sent from a worker per plugin, so a slow or hung plugin never stalls the window.
- A plugin a repository names loads only once you trust its SHA-256 digest (
liquify plugin trust), from a trust store outside every repository.
Optional
- Multiplayer presence and attribution.
- An AI assistant, off by default. Off, it constructs no provider and opens no connection. Its context is shown before sending, and a proposed edit applies only when you accept it.
Command line
liquify [PATH], --lake URL PATH, --print-tree, --apply-edits, --smoke, --screenshot, --command NAME, plugin trust, plugin list, docs commands|keymap, and version.
What it does not include
- No signed installers. The packaging scripts exist (
packaging/), but this release publishes none. - No version pairing with liquid by tag: liquify names the exact liquid commit it builds against.
- One lake per repository; choosing among several lakes is not built (#96).
Known issues
Security first.
-
A plugin worker test segfaults:
PluginDispatcher.EventsAreDeliveredOnTheWorker(#181). An AddressSanitizer run is under way; its report goes on the issue. -
Accepted assistant edits are signed as you, not as the assistant acting for you (#74). The liquid API that fixes it is in review (liquid#542).
-
Plugin sandboxes do not deny reads, and Windows has no network sandbox (plugins).
-
A repository another liquid process writes to can fail to open or lose its index, which shows as an empty Quick Open now and then (#97). The fix is in liquid (liquid#532) and reaches liquify with the next liquid pin.
-
Recording a build on macOS may need a filesystem extension liquid's sandbox uses.
-
A few toolbar labels and tooltips show a key's default binding after a rebind (#156).
-
Opening a file can set the status to "no symbol references found" though nothing was searched (#158).
-
Four headless screenshot tests fail (#182).
-
15 of 23 native window scenarios failed in the release run, on a heavily loaded machine; each is being rerun alone to separate dropped events (#161) from defects (#183).
-
The Linux and Windows builds are exercised less often than macOS.
Where it has run
macOS 14 (Apple silicon, Metal, Retina), from source. No installer was published.
Verification
Run on the release tree (dev at the cut, liquid 27d56ba), macOS 14 on Apple silicon, Release build with native window tests on, load average 130 to 190 on 16 cores. Tracked in #168.
| Proof | Result |
|---|---|
| Build, every target including tests | Passes; liquify version reports 0.1.0+<revision> |
Unit and headless suite (ctest -E native, -j8) |
203 of 208 passed; 4 failed (#182), 1 segfault (#181); 0 skipped |
| Native window scenarios (serial) | 8 of 23 passed, 15 failed (#183); 1 skipped (launch-1, no density-1 display); 1 disabled (front-door-clone-push) |
| AddressSanitizer | Running for the segfault; report on #181 |
| Linux, Windows | Not run for this release |
The release was cut on the maintainer's word with these failures open and listed.