Known limitations

What doesn't work yet at 0.9, and what is deliberately absent.

On this page

Lattice 0.9 is an alpha. This page is the honest list — check it before filing an issue, and file anyway if your case is worse than what's written here.

Distribution

  • Binaries are unsigned. macOS quarantines browser downloads; clear it with xattr -dr com.apple.quarantine <dir>. No .dmg, no .msi, no notarisation — those need a paid certificate.
  • No Homebrew, no cargo install. Use the install script or a release archive. See installation.
  • ARM Linux and ARM Windows GUI builds are best-effort and may be missing from a release. The terminal build is available on every platform.
  • Windows executables have no embedded icon.

Editor

  • The window is the default from 0.9.8; --tui opens the terminal. Both are first-class. A few things the terminal does are not in the window yet: input-method and dead-key composition, inline completion ghost text, and some document-highlight styling.
  • LSP servers must be installed by hand. There is no server manager or installer; point lattice at servers already on your PATH.
  • Org-mode is a separate build. It ships as an out-of-repo WASM plugin (dhruvasagar/lattice-org-plugin) you clone and build yourself — it is not bundled with the editor or the installer.
  • The Claude Code and opencode integrations need their own CLI installed. :claude requires the claude CLI on your PATH; :opencode requires the opencode CLI. Lattice provides the editor-side integration, not the agent itself.
  • Concealment has no settings. Markup hiding works and both renderers paint it, but there is no conceallevel / concealcursor equivalent: the cursor line reveals in Insert and Replace, always, and only org declares conceal rules today.
  • No crash reporter, and no accessibility work has been done yet.

Grammar and commands not yet implemented

  • In :!cmd: % / # for file names, :!!, and :r !cmd.
  • A few ex-range forms: ; between addresses, \/ / \? / \&, and *. Everything else in ranges works. Range commands beyond :d, :y, :>, :<, :s, :g and :narrow — :m, :t, :normal, :sort, :j — do not exist yet.
  • A substitute with a range other than % has no live preview.
  • Completion inside :s/.../.../.
  • :autocmd / :add-hook.
  • :customize — browsing and picking groups/modes works, and :customize-edit <name> opens the option in the : line via :set; there is no TOML write-back, so a change made this way is not persisted back to your config file.
  • :history-* (the dashed spelling) does not exist; use :history [commands|searches|pane-buffers] instead — it ships today with all three kinds.
  • Terminal buffers: mouse passthrough.

Deliberately absent

  • No vimscript, no Lua, no elisp. WASM is the single extension substrate; your config is Rust compiled to WASM (init). This is a design decision, not a gap. Its cost is that a programmable config needs a Rust toolchain with the wasm32-wasip2 target on the machine that runs the editor — the editor itself does not, and lattice --scaffold-init tells you what is missing.
  • No vim/emacs config compatibility. Explicit non-goal.
  • Rich inline media (images, embedded widgets) is post-1.0.

Reporting

Open an issue with your platform, lattice --version, and whether :plugins lists the four bundled plugins. If it doesn't, say so — that is its own bug and it hides others.