Lapce
Lapce 0.4.6 is a cross-platform code editor built with Rust, Floem and wgpu, with LSP, terminal, optional Vim-style modal editing, SSH remote development and WASI plugins.
What Lapce is for
Lapce targets developers who want a lightweight native editor with LSP intelligence, an integrated terminal, SSH remote development and optional Vim-style modal editing. It uses a native rendering stack and can run language tools and plugins in a local or remote workspace.
Version and platform boundary
Lapce 0.4.6 is the stable release with Windows x64 MSI and portable packages, macOS DMG, Linux x64 and ARM64 archives, and distribution packages. Nightly builds should remain separate from important projects and existing configuration backups.
Plugins and remote development
WASI plugins are not automatically trustworthy: they can receive host capabilities supplied by the editor. SSH mode uses the system ssh client and starts lapce-proxy on the remote host, where plugins and commands may also execute. Verify host keys, proxy source, account permissions and the remote working directory before editing.
Maintenance note
Review date: 2026-08-06. The page was checked against the 0.4.6 stable packages, LSP and terminal workflow, SSH proxy behavior, plugin boundary and configuration migration.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Lapce to this cloud drive
Baidu Netdisk
Save Lapce to this cloud drive
Lapce 0.4.6 installation, LSP and SSH remote-development guide
Install the stable package that matches the operating system and architecture, test editing, terminal and language services locally, then use a controlled SSH host to verify the remote proxy and reconnect behavior.
Before you start
- Confirm the operating system and CPU architecture, matching Linux packages to the distribution and architecture or choosing a portable archive.
- Back up editor settings, shortcuts and uncommitted project changes so first indexing or formatting cannot overwrite the only copy.
- Prepare a working OpenSSH client, verified host fingerprint, SSH key and low-privilege remote account before remote development.
Installation steps
- 01
Choose the 0.4.6 stable package
Use Windows MSI or portable ZIP, macOS DMG, or the Linux DEB, RPM or generic archive; keep Nightly builds separate from the stable installation.
- 02
Complete a local first launch
Open a test project, check font scale, GPU rendering, file tree, terminal and shortcuts, then adjust theme and editing behavior from the settings panel.
- 03
Install only needed language support
Review publisher, update date and runtime location for each plugin or language server, then test completion, diagnostics, navigation and formatting in a disposable project.
Quick start
- 01
Establish the local workspace
Open the project root, wait for indexing, inspect version-control changes and only then enable save-time formatting or automatic fixes.
- 02
Verify terminal and LSP
Run read-only checks in the terminal and open a file with diagnostics, confirming that completion, definition jumps and code actions come from the expected server.
- 03
Connect to a controlled SSH host
Use a configured Host or explicit user and hostname, verify the first host key, confirm `lapce-proxy` starts remotely and check that plugins and file operations target the intended server.
Usage tips
- Remote mode starts a proxy and runs plugins and commands in the remote environment; do not open an untrusted repository with an elevated account.
- Lapce delegates SSH configuration and keys to the system client, so test the same connection in a terminal before deleting keys or relaxing host-key checks.
- Back up settings and shortcuts before upgrades and test stable and Nightly builds separately.
Troubleshooting and uninstall
Why can a remote connection open but not a directory in the interface?
A recent interface rewrite can affect remote folder opening. Use the remote terminal to start Lapce with the target path, then confirm that the workspace belongs to the current connection.
Why does the UI flicker, scale incorrectly or fail to launch?
Confirm version 0.4.6 and the correct architecture, reset custom scale and update the graphics driver, then test with an empty configuration to separate GPU, theme and plugin issues.
- Back up configuration and project stateSave settings, shortcuts and plugin lists, commit or back up unfinished code and record where Lapce installed its remote proxy.
- Remove the application and remote proxyUninstall the local app or delete its portable directory, clear user settings if appropriate and remove the remote proxy only after confirming that no session needs it.
Frequently asked questions
Is Lapce 0.4.6 a stable release or Nightly?
0.4.6 is the stable release, while builds with commit identifiers are pre-release Nightly artifacts. Keep a rollback and configuration backup before testing Nightly in an important project.
Does Lapce remote development support SSH passwords?
The normal graphical path uses SSH keys and the system ssh client. Configure keys, host fingerprints and a least-privilege account, and use an interactive terminal only for a deliberate compatibility case.
Are Lapce plugins fully isolated?
WASI execution does not mean unconditional trust. Plugins receive host capabilities exposed by the editor, and remote plugins and commands run on the remote machine, so review source, permissions and maintenance status.