Download
One portable installer.
The application is embedded in the installer at build time, so there is no runtime to install first and no payload to fetch afterwards. No account, and nothing to configure beyond adding a provider key.
Loom 0.1.0
not released yetNothing has been tagged yet, so there is no installer to hand you. 0.1.0 is the version in development, and the front page describes what the build in the repository already does.
- Platform
- Windows 10 or 11, 64-bit
- File size
- —
- Update signature
- unsigned — the application will refuse to auto-update from it, which is the intended behaviour
- Payload SHA-256
- published in the release notes once a release exists
The button points at /download/latest, which is this site’s own route and always resolves to whichever release is newest — so a link you copy into an issue keeps working after the next version ships. Releases live at aaen-studios/loom.
Why Windows says the publisher is unknown
The installer is not code-signed. A Windows code-signing certificate is a recurring cost, and until one is in place SmartScreen shows the same generic warning for any installer that lacks it, regardless of what the installer does. So the honest substitute is to verify the file yourself rather than to trust the absence of a warning.
# in the folder you saved the installer Get-FileHash .\Loom-Setup-<tag>.exe -Algorithm SHA256 # compare against the hash in the release notes https://github.com/aaen-studios/loom/releases
This is separate from the updater, and the updater is the stronger of the two. The payload an update installs is signed with minisign and verified before anything is applied, so an update cannot be tampered with in transit even though the installer that delivered it cannot prove who built it. The one thing a hash cannot tell you is who wrote the code — and that is what the public repository is for.
After installing
Add a provider key in Settings → Providers and pick a model in the composer. To skip the key entirely, install Ollama or LM Studio and point Loom at it — local models are detected rather than configured. The second movement of the front page covers the window and the last one answers the questions worth asking first.
Uninstalling
Either add or remove programs, or run %LOCALAPPDATA%\Loom\uninstall.cmd. Your chats, keys and settings are deliberately left in place; the privacy page lists exactly what remains and where.