Litria
Download
Home/get2

Install notes

What your OS will say, and why

Litria's builds are unsigned. This page exists so nothing about the first run is a surprise.

  1. 01

    Download the artifact for your platform

    Windows takes the .exe unless you manage installs centrally, in which case take the .msi. macOS picks by chip. Linux: the AppImage runs anywhere without root.

  2. 02

    Clear the first-run warning

    Every build is unsigned, so each OS interrupts once. None of these are a security finding about Litria specifically — they are what every unsigned application looks like.

  3. 03

    Open any folder

    There is no project format to convert to. Point Litria at an existing folder and it bootstraps a workspace on first open — pieces for files, groups for folders, wires read from your imports.

Platform status
  • Windows x64 — the build the developer uses every day. Treat this as the reference platform.
  • macOS has been launched and run by a tester on one machine — enough to say it works, not enough to call it proven. Linux passed the parity checklist on Fedora 44 as a source build, but as of v1.1.1 no human has launched the packaged AppImage, deb, or rpm. Please say so when either does not work.

shippednew in 1.1.1known caveatplanned

Prerequisites

None for the app itself — Node.js, Pyright, and typescript-language-server are bundled in the installer.

One optional extra: Python intelligence resolves imports better if Python 3.8+ is on your PATH, because Pyright needs to see your environment. Without it you still get hover, completions, and diagnostics for single files.

Uninstalling

Litria writes project state into a workspace.db beside each project and preferences into ~/.litria/. Removing the app leaves both; delete them by hand if you want a clean slate. Nothing is written outside those two places.