[!IMPORTANT] Transparent analytics in v0.2.1

Lilo uses two separate sources of product statistics:

• Optional application analytics: only after explicit consent, Lilo sends a random installation UUID, the local calendar date, the application version and daily numeric counters from a fixed feature whitelist. The counters are sent periodically to a Cloudflare Worker and stored in D1. Analytics can be disabled at any time from Settings, which also queues deletion of that installation's existing rows.
• GitHub repository traffic: a daily GitHub Action archives the repository-level views, unique visitors, clones, referrers and popular paths returned by GitHub's Traffic API. This is separate from the desktop application and contains no Lilo installation identifier.

Lilo does not send note contents, titles, filenames, vault paths, tags, aliases, search text, Quick Capture text, wiki-link targets, device identifiers or account details. The Worker does not store request IP addresses in D1.

The complete implementation is public: desktop whitelist and payload, Cloudflare Worker, D1 schema, GitHub traffic workflow and the full privacy notice.

Exact application feature whitelist (21 counters)

note_created, daily_note_opened, quick_capture_saved, template_note_created, template_inserted, markdown_formatting_used, search_used, saved_search_created, command_palette_used, wiki_link_opened, graph_opened, tag_filter_used, attachment_added, note_pinned, folder_created, trash_restored, backup_restored, markdown_imported, vault_exported, zen_mode_enabled and always_on_top_enabled.

One app, two scales

Lilo is designed around a simple idea: opening a note should not force you into a large, distracting application. Keep it as a small always-on-top widget for quick writing, or expand it into a workspace with your vault explorer, editor and contextual inspector.

Everything you need without leaving the widget

A daily workflow that remains plain Markdown

Open today's note with Alt+D. If it does not exist, Lilo creates it; if it already exists, Lilo opens the same file. The Yesterday and Tomorrow controls let you move through the journal without searching the vault manually.

Daily filenames use standard date formatting. They can stay flat:

Daily/2026-08-18.md

or be organised into portable nested folders:

Daily/2026/08/18.md

Quick Capture adds a timestamped entry without making you switch away from the note you are reading. Its destination is configurable:

• today's daily note;
• Inbox.md;
• a new timestamped note;
• a selected custom note.

On Windows, the configurable global shortcut can bring Lilo forward and open Quick Capture even when another application is focused. Linux keeps the in-app shortcut; a system-wide Linux implementation is not included in 0.2.1.

Templates without lock-in

Templates are ordinary Markdown files inside the configurable Templates folder. They can be used to create a new note or inserted into the active note.

# {{title}}

Created: {{datetime}}

## Focus

{{cursor}}

## Notes

Supported variables:

Template frontmatter is not copied over existing note metadata, and templates never execute scripts.

Find notes by meaning and structure

Simple text search works as expected. When the vault grows, focused operators can be combined:

tag:rust path:"Programming Notes" link:"Ownership" title:"Memory" borrowing

All conditions in a query are applied together, so a broad vault can be narrowed quickly.

Tag filters accept comma-separated values and negation, for example:

tag:rust,learning -tag:archived

Attachments without a media database

Drop an image into the editor or paste a screenshot to copy it into the configurable Attachments folder. Lilo inserts a relative Markdown image link and renders PNG, JPEG, GIF, WebP and SVG files inline. Other files can remain ordinary relative Markdown links.

Imported files never silently replace an existing file with the same name. The orphan inspector lists files that are no longer referenced before the user chooses whether to remove them. Attachment paths are constrained to a relative directory inside Notes so a cleanup cannot scan outside the vault.

Markdown-first storage

Lilo stores content as .md files with YAML frontmatter. Preferences and interface state stay separately in settings.json.

Vault/
├── Notes/
│   ├── Daily/          Daily notes
│   ├── Templates/      Reusable Markdown templates
│   ├── Attachments/    Images and linked local files
│   └── ...             Your own folders and notes
├── Trash/              Recoverable deleted notes
└── Backups/            Rotating note backups

There is no embedded note database and no proprietary content format. Notes can be inspected or edited in another text editor; Lilo detects external changes before overwriting a locally modified note. Vault-wide operations create recoverable data where appropriate.

Keyboard-first control

Core note, search, graph and save shortcuts can be changed in Settings. The Command Palette also exposes actions that do not need a permanent toolbar button or dedicated shortcut.

Install Lilo

Download the latest packages and matching SHA-256 files from GitHub Releases.

Windows

• Lilo-0.2.1-windows-x64-setup.exe — per-user installer with a Start menu shortcut; administrator access is not required.
• Lilo-0.2.1-windows-x64.zip — portable archive for manual installation.

The current binaries are not code-signed, so Windows SmartScreen may display a warning. WinGet distribution is prepared but remains unavailable until the initial package is accepted into the community repository.

Linux

• Lilo-0.2.1-ubuntu-22.04-x86_64.tar.gz — Ubuntu 22.04 or newer.
• Lilo-0.2.1-arch-x86_64.tar.gz — current Arch Linux.

sha256sum -c Lilo-0.2.1-<platform>-x86_64.tar.gz.sha256
tar -xzf Lilo-0.2.1-<platform>-x86_64.tar.gz
cd Lilo-0.2.1-<platform>-x86_64
install -Dm755 Lilo "$HOME/.local/bin/Lilo"
"$HOME/.local/bin/Lilo"

Install the executable in its final location before enabling autostart. Lilo uses the Windows per-user Run registry value or a Linux XDG autostart entry, depending on the platform.

For updating, portable use and recovery instructions, see RELEASE.md.

Build from source

Install the stable Rust toolchain, then run:

git clone https://github.com/HellterEnjoy/Lilo.git
cd Lilo
cargo run --release

Ubuntu and related distributions also require the native windowing dependencies:

sudo apt-get update
sudo apt-get install libssl-dev libwayland-dev libxcb-render0-dev \
  libxcb-shape0-dev libxcb-xfixes0-dev libxkbcommon-dev \
  libxkbcommon-x11-dev pkg-config

Run the project checks with:

cargo fmt --all -- --check
cargo test
cargo clippy --all-targets -- -D warnings

Official Windows release artifacts are built from the version tag on a clean GitHub Actions runner. For local packaging, Inno Setup 6 and scripts/package-windows.ps1 produce the same installer, portable ZIP and SHA-256 files.

Platform status

Windows and Ubuntu run formatting, tests and Clippy in CI. Linux releases are currently manual archives rather than native distribution packages.

Project status

Version v0.2.1 adds explicit opt-in usage analytics with a public event whitelist, in-app deletion and a separate GitHub traffic archive. It also improves compact-window layout, adds configurable autosave and defers expensive link and tag index refreshes while typing. Lilo does not yet provide automatic updates, code signing, native Linux packages, a system-wide Linux capture hotkey or an official macOS build.

• Roadmap — planned product direction;
• Changelog — implemented release history;
• Release guide — installation, updates and recovery;
• Performance notes — current performance guardrails.

Feedback and contributions

Bug reports, feature requests, UI/UX feedback and technical suggestions are welcome through GitHub Issues.

Lilo is intentionally maintained as a single-author project, so code pull requests are not accepted into the official codebase. Forking and modifying the project remains welcome under the license terms. See CONTRIBUTING.md for the complete policy.

License

Lilo is source-available under the PolyForm Noncommercial License 1.0.0.

You may use, study, modify, fork and redistribute Lilo and modified versions for non-commercial purposes, subject to the license terms. Commercial use requires separate permission from the copyright holder. Required copyright, license and attribution notices must remain intact when redistributed.

Copyright © 2026 Kyrylo Yazynin · github.com/HellterEnjoy/Lilo