-
AI chat routes through SSH and Reticulum. An OPENAI profile gains an AI-route setting next to its endpoint: Direct (default), Via SSH, or Via Reticulum. Via SSH opens a local port forward through a connected SSH carrier profile — jump-host auth and prompts included — and the chat's HTTP dials the loopback forward while URL rewriting stays off, so TLS hostname verification still runs against the real endpoint name. Via Reticulum forwards over a connected Reticulum carrier the same way; the carrier must already be connected (a forward-only consumer can't keep the RNS stack alive by itself). A route and tunnel/proxy routing are mutually exclusive — setting one clears the other. The route is torn down on every disconnect path: disconnecting the endpoint closes its forward, and a carrier dying fails the endpoint's sessions and drops the forward, so the next send refuses until a fresh connect rather than silently bypassing the route.
-
Chat images from the Files tab. The chat attach sheet gains a Files option alongside gallery and camera: pick a file from any Files-tab backend to attach. Files above 20 MiB are rejected with the size shown; the pick banner has a Cancel, and cancelling leaves no staged attachment.
-
Take photo from the terminal attach sheet. The terminal paperclip sheet gains a Take photo option next to send-file and the scanner entries: the capture rides the existing send-file path, uploading through the Files tab and inserting the remote path at the cursor.
Which APK?
haven-<version>-<abi>-release.apk — the full app, and what F-Droid
carries. If in doubt, take this one.
haven-<version>-<abi>-terminal-release.apk — the same app with the
desktop and media parts left out, for people who only use Haven for SSH,
terminals, files and storage. Less than half the size on arm64. It drops
RDP and SPICE remote desktop, the native Wayland desktop, and ffmpeg — so
no media conversion, and no video previews or streaming in the file
browser. VNC is kept, so a Linux desktop running inside Haven's guest
still works.
Both are signed with the same key and carry the same version number, so
you can install either over the other without losing connections, keys or
your Linux guest. The shared version number does mean an updater will not
offer to move you between them — switching is a deliberate download.
<abi> is your device's CPU: arm64 for essentially every modern phone,
armv7 for older 32-bit devices, x64 for emulators.
Full Changelog: v5.88.0...v5.89.0