Releases: Fortemi/HotM
Release list
HotM 2026.5.7
HotM 2026.5.6
HotM 2026.5.5
HotM 2026.5.4
HotM 2026.5.3
Install — one command on Linux
curl -fsSL https://raw.githubusercontent.com/Fortemi/HotM/main/scripts/install.sh | bashThis installs everything: PostgreSQL 18 (via PGDG), pgvector, postgis, the HotM .deb, the Ollama daemon, and pulls the embedding + generation models in the background. Idempotent — re-runnable. Drop-in replacement for v2026.5.2.
Audit before piping:
curl -fsSL <url> | less
After install, launch with hotm. See quick-start docs for the 2-minute version or the full Linux install guide for manual setup, troubleshooting, and installer flags.
Other platforms
| Platform | Command |
|---|---|
| macOS | Download HotM_2026.5.3_aarch64.dmg below, drag to /Applications, then xattr -cr /Applications/HotM.app |
| Linux .deb (manual) | sudo apt-get install ./HotM_2026.5.3_amd64.deb (requires PGDG repo + Postgres 18) |
| Linux AppImage | chmod +x HotM_2026.5.3_amd64.AppImage && ./HotM_2026.5.3_amd64.AppImage |
| Docker UI | docker pull ghcr.io/fortemi/hotm-ui:2026.5.3 |
What's new
Cleanup release on top of v2026.5.2's installer rework:
- Fix:
install.shnow defensively recreates/usr/share/ollamaafter the upstream Ollama install. Resolves a crash-loop on dirty re-installs where theollamasystem user persisted from a prior install but the data dir was wiped. - Removed:
scripts/setup-linux.sh(deprecated in v2026.5.2, deleted here). - Docs:
docs/quick-start.mdrewritten around the single-command install path.
Full release notes: docs/releases/v2026.5.3.md
Compatibility
Identical to v2026.5.2. PostgreSQL 18 still required.
HotM 2026.5.2
Install — one command on Linux
curl -fsSL https://raw.githubusercontent.com/Fortemi/HotM/main/scripts/install.sh | bashThis installs everything: PostgreSQL 18 (via PGDG), pgvector, postgis, the HotM .deb, the Ollama daemon, and pulls the embedding + generation models in the background. Idempotent — re-runnable.
Audit before piping:
curl -fsSL <url> | less
After install, launch with hotm. See quick-start docs for the 2-minute version or the full Linux install guide for manual setup, troubleshooting, and installer flags.
Other platforms
| Platform | Command |
|---|---|
| macOS | Download HotM_2026.5.2_aarch64.dmg below, drag to /Applications, then xattr -cr /Applications/HotM.app |
| Linux .deb (manual) | sudo apt-get install ./HotM_2026.5.2_amd64.deb (requires PGDG repo + Postgres 18) |
| Linux AppImage | chmod +x HotM_2026.5.2_amd64.AppImage && ./HotM_2026.5.2_amd64.AppImage |
| Docker UI | docker pull ghcr.io/fortemi/hotm-ui:2026.5.2 |
What's new
This is the installer rework release. Single-command Linux install, .deb postinst that seeds the matric database on apt's behalf, PostgreSQL 18 standardization. Tracking issue: #196.
Full release notes: docs/releases/v2026.5.2.md
Compatibility note
uuidv7(), a PG 18 built-in. The bootstrap installer adds the PGDG repo and pulls PG 18 automatically; users on PG 13–17 must upgrade. See matric-api portability tracking issue.
Verification
| Asset | SHA-256 |
|---|---|
HotM_2026.5.2_amd64.deb |
see SHA256SUMS.txt |
HotM_2026.5.2_amd64.AppImage |
see SHA256SUMS.txt |
HotM_2026.5.2_aarch64.dmg |
see SHA256SUMS-macos.txt |
End-to-end validated on a clean Ubuntu 25.10 (questing-pgdg) host.
HotM 2026.5.1
Patch release — one breaking change for embedders, plus documentation cleanup.
This release removes the legacy host-adapter fallback symbol and finishes a documentation cleanup. No Fortemi API contract changes; pairs with Fortemi v2026.5.0 unchanged.
⚠️ Breaking change for embedders
Legacy host-adapter fallback removed
In v2026.5.0 the runtime accepted host adapters published under a legacy symbol name as a deprecated fallback (with a console warning). That fallback is removed in v2026.5.1. The runtime now only reads window.__HOTM_HOST__.
Action required only if your embedding shell still publishes the host adapter under a non-canonical window property. If your shell already publishes window.__HOTM_HOST__ (the canonical name documented since v2026.4.2), you don't need to do anything.
To migrate, publish the host adapter under the canonical name:
(window as any).__HOTM_HOST__ = adapter;If your embed code currently assigns the adapter to a different window property, rename the assignment target to __HOTM_HOST__. See docs/host-adapter.md for the full contract.
📝 Documentation cleanup
Historical project-name references removed from public-facing docs (README.md, CHANGELOG.md, docs/host-adapter.md, docs/releases/v2026.4.1.md, docs/releases/v2026.5.0.md). Internal CI build paths on the macOS build host are unaffected.
📦 Upgrade notes
Drop-in replacement on every platform — no migration required for end users.
Linux (.deb / AppImage)
sudo apt-get install ./HotM_2026.5.1_amd64.debOr the AppImage:
chmod +x HotM_2026.5.1_amd64.AppImage
./HotM_2026.5.1_amd64.AppImagemacOS
hdiutil attach HotM_2026.5.1_aarch64.dmg
cp -R "/Volumes/HotM/HotM.app" /Applications/
hdiutil detach "/Volumes/HotM"
xattr -cr /Applications/HotM.appWindows
NSIS installer drop-in replace.
Docker UI image
docker pull git.integrolabs.net/fortemi/hotm-ui:2026.5.1Pair with git.integrolabs.net/fortemi/matric-api:2026.5.0 for the matched-version stack.
🤝 Compatibility
| Component | Version |
|---|---|
| Fortemi (matric-api) | 2026.5.0 (matched, unchanged from HotM v2026.5.0) |
| Earlier Fortemi versions | 2026.4.x — supported (no contract changes) |
| Host adapter contract | v1, canonical __HOTM_HOST__ symbol only |
🧪 Verification
act_runner exec -j quality-gate -W .gitea/workflows/ui-ci.yml → 94 test files passing prior to tagging.
SHA256
96c640dff4372b5200ab7c2d3e4f420a2b5ff7ee59ebe2c6288ef810984ad955 HotM_2026.5.1_aarch64.dmg
d539c797d4e612330a7e2f9224c5bf511ea424e570e0711c5ce9f8ae1f0bd961 HotM_2026.5.1_amd64.AppImage
757e5ba1f8d31c3330154386f82ac0fbd95b6bd0390e5f505b3b659417e039cb HotM_2026.5.1_amd64.deb
(See SHA256SUMS.txt and SHA256SUMS-macos.txt attachments.)
📝 Full release notes
docs/releases/v2026.5.1.md · CHANGELOG.md
Compare: v2026.5.0...v2026.5.1
HotM 2026.5.0
Minor release — version-aligned with Fortemi v2026.5.0. No HotM API contract changes.
This release pairs the desktop bundle and Docker UI image with the matched Fortemi v2026.5.0 sidecar (filesystem attachment durability + CI Docker fix on the Fortemi side). HotM-side changes since v2026.4.1 are limited to host-adapter compatibility, macOS install polish, CI fixes, and an AIWG framework refresh.
🔗 Version alignment with Fortemi v2026.5.0
HotM and Fortemi share a release cadence; v2026.4.1 → v2026.5.0 is the catch-up to Fortemi's minor bump. The Fortemi sidecar shipped in this release contains:
- Filesystem attachment durability (Fortemi-side)
- CI Docker pipeline fix (Fortemi-side)
Nothing on the HotM API contract changed.
🛠 What's changed in HotM
__HOTM_HOST__ adapter — legacy injection-point compatibility (#192)
Third-party shells that embed HotM using the previous __HOST__-style injection-point name now work unmodified. The runtime accepts both injection-point names and forwards the version field through to the host adapter so embedders can detect protocol revision. Fix for embedders who pinned the previous name during the host-adapter rename.
macOS install polish
setup-macos.shis now at full parity withsetup-linux.sh(sidecar staging,.envhandling, Ollama detection, port allocation).- The install docs and post-install script walk users through the System Settings → Privacy & Security Gatekeeper approval needed for the self-signed
.appbundle on first launch.
CI
ui-ci.yml checkout aligned with the Fortemi workflow pattern (#191), eliminating an intermittent ${GITHUB_SERVER_URL} resolution failure that surfaced under local act_runner execution.
AIWG framework refreshed (internal)
AIWG bumped to 2026.4.0-rc.31. The Codex provider deployment is dropped from this repo's AIWG configuration; Claude Code remains the supported provider.
📦 Upgrade notes
Drop-in replacement on every platform — no migration required.
Linux (.deb / AppImage)
sudo apt-get install ./HotM_2026.5.0_amd64.debOr the AppImage:
chmod +x HotM_2026.5.0_amd64.AppImage
./HotM_2026.5.0_amd64.AppImagemacOS
hdiutil attach HotM_2026.5.0_aarch64.dmg
cp -R "/Volumes/HotM/HotM.app" /Applications/
hdiutil detach "/Volumes/HotM"
xattr -cr /Applications/HotM.app # clear Gatekeeper quarantineIf this is your first install of a self-signed HotM build, follow the Gatekeeper approval flow in docs/installation/macos.md. scripts/setup-macos.sh handles the xattr -cr automatically and is idempotent.
Docker UI image
docker pull git.integrolabs.net/fortemi/hotm-ui:2026.5.0Pair with git.integrolabs.net/fortemi/matric-api:2026.5.0 for the matched-version stack.
🧪 Verification
act_runner exec -j quality-gate -W .gitea/workflows/ui-ci.yml → exit code 0 prior to tagging. UI tests, type check, build, security audit (non-blocking), and SBOM generation all green.
SHA256
3846d61e70bc8b36f736da29d9811c0ef2e3f940f16316435209ceb8b2aa38e0 HotM_2026.5.0_aarch64.dmg
9b9db25d2458f12c582845194fb405a47baf72aa28823890755e550c91724bf3 HotM_2026.5.0_amd64.AppImage
ea4d6c282918d9f26009d2bd3b079849d292f1e07706efa7f830494634a29594 HotM_2026.5.0_amd64.deb
(See SHA256SUMS.txt and SHA256SUMS-macos.txt attachments.)
🤝 Compatibility
| Component | Version |
|---|---|
| Fortemi (matric-api) | 2026.5.0 (matched) |
| Earlier Fortemi versions | 2026.4.x — supported (no contract changes) |
| Embedding shells using the legacy host injection-point name | Now compatible (was: required rename) |
📝 Full release notes
docs/releases/v2026.5.0.md · CHANGELOG.md
Compare: v2026.4.1...v2026.5.0
HotM 2026.4.1
Patch release — bug fixes only, no breaking changes.
This release addresses two issues discovered during desktop install validation against v2026.4.0. Both are user-visible blockers for first-run experience; recommended for all users on v2026.4.0.
🐛 Fixed
Admin Panel "Test Connection" no longer fails on a healthy backend
In v2026.4.0, clicking Admin → Inference → Test Connection returned Connection Failed: Bad Request even when Ollama and the bundled matric-api sidecar were both running and reachable. Same story for note creation, configuration writes, and any agent tool call that carried a JSON body — all of them hit the backend with Content-Type: application/json and zero bytes of body.
Root cause: Tauri v2 defaults command-argument deserialization to camelCase. The hotm_fetch Rust handler accepts a snake_case body_b64: Option<String>, but the documented HotmHostAdapter contract sends the body as body_b64. Tauri silently dropped the unrecognized snake_case key, so hotm_fetch received body_b64: None and reqwest produced a body-less request. GET requests were unaffected.
Fix: #[tauri::command(rename_all = "snake_case")] on hotm_fetch, so the documented snake_case JS contract works end-to-end.
Bundled sidecar moved to a HotM-namespaced path (closes #187)
The Tauri-bundled Fortemi sidecar binary now installs as hotm-matric-api instead of matric-api:
| Platform | Path |
|---|---|
| Linux (.deb / AppImage) | /usr/bin/hotm-matric-api |
| macOS | HotM.app/Contents/MacOS/hotm-matric-api |
| Windows | hotm-matric-api.exe alongside hotm.exe |
This eliminates the /usr/bin/matric-api collision with sibling Tauri apps that bundle their own copy of matric-api. Installing v2026.4.1 alongside such a package no longer requires dpkg --force-overwrite.
The upstream Fortemi sidecar release artifact name (matric-api-<triple>) is unchanged; CI workflows rename at stage time.
📦 Upgrade notes
Linux
sudo apt-get install ./HotM_2026.4.1_amd64.debIf you previously installed v2026.4.0 with dpkg --force-overwrite to resolve a sibling-package conflict on /usr/bin/matric-api, this upgrade removes that file (it's no longer in HotM's package contents). Restore it for the sibling app with:
sudo apt-get install --reinstall <sibling-package>After that, both apps coexist cleanly: hot-m owns /usr/bin/hotm-matric-api, the sibling owns /usr/bin/matric-api, no overlap.
macOS
hdiutil attach HotM_2026.4.1_aarch64.dmg
cp -R "/Volumes/HotM/HotM.app" /Applications/
hdiutil detach "/Volumes/HotM"
xattr -cr /Applications/HotM.app # clear Gatekeeper quarantineThe updated scripts/setup-macos.sh now does the xattr -cr automatically and is idempotent — safe to re-run on each upgrade.
MCP / agent integrations
Update any explicit references to the bundled sidecar binary path:
| Old | New |
|---|---|
/usr/bin/matric-api --mcp |
/usr/bin/hotm-matric-api --mcp |
/Applications/HotM.app/Contents/MacOS/matric-api --mcp |
/Applications/HotM.app/Contents/MacOS/hotm-matric-api --mcp |
pkill -f matric-api |
pkill -f hotm-matric-api |
🧪 Verification
| Platform | Validated |
|---|---|
| Ubuntu 24.04 | clean install over pre-existing sibling .deb (no --force-overwrite needed); Admin Panel Test Connection returns 200 with 7 Ollama models detected |
| macOS aarch64 (mutsu) | DMG install, prereq script exits with all green, Test Connection succeeds |
SHA256:
4e9c0145f79251164ae0b72aae22803769984c6d5bf703ce03de86d037b9f1cc HotM_2026.4.1_aarch64.dmg
(See SHA256SUMS.txt and SHA256SUMS-macos.txt attachments for full list.)
🔮 Open follow-ups
- #186 — default Ollama generation model: scripts pull
qwen3.5:9b(newer family); v2026.4.0 release notes claimqwen3:14b. Three resolution options under discussion. - #187 — partial fix shipped here; full Debian-Policy-clean relocation to
/usr/lib/hot-m/hotm-matric-apideferred until Tauri'sexternalBinsupports private install paths.
📝 Full release notes
docs/releases/v2026.4.1.md · CHANGELOG.md
Compare: v2026.4.0...v2026.4.1