- 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.
- 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.
- 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.
- Windows x64 — the build the developer uses every day. Treat this as the reference platform.
- macOS and Linux — these compile and pass the full test suite in CI, but as of v1.0.1 no human has launched either artifact. They should work. Please say so when they do not.
shipped new in 1.0.1 known caveat planned
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.
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.