Known issues
What we know is open.
Confirmed issues with their live status on the project’s issue tracker, newly reported bugs, and stated limits. This list is not a statement that everything else works.
Status checked against GitHub Nov 16, 1:20 PM UTC. Rechecked every few hours.
Still open · 2
- #55
Stale Desktop lease after the client admission fix
BugA stale Hermes Desktop lease has been observed after a client admission fix. Reproduction and resolution are still open.
Open on GitHub for 53 days
- #61
OAuth-only gateway sign-in is not supported
LimitationGateways that only offer provider OAuth sign-in cannot be used yet. Session token, loopback token, and username and password strategies work where the gateway supports them.
Open on GitHub for 49 days
Reported since · 1
Open bugs on GitHub that aren’t written up here yet. Titles are as reported.
- #212
Hermes messages are stuck on a few threads
BugReported Oct 26, 2026 · open 21 days
Fixed in the source · 2
Closed on GitHub since this list was written. A fix reaches TestFlight users in a later build.
- #62
HTTP gateway warning wording is unclear for encrypted tunnels
BugIf your gateway is reached over an encrypted tunnel but addressed with http://, the warning copy can read as if the connection is unprotected. The wording needs to explain the tunnel case.
Closed as completed on Oct 20, 2026. The fix is in the source; check the changelog for the build that carries it.
- #82
File protection for local database sidecar files and staging areas
Security hardeningFile protection and backup exclusion are not yet applied to the SQLite -wal and -shm files, the store directory, bridged-room data, and artifact staging. This is security hardening in progress. The stored data is non-secret, and credentials are in the Keychain.
Closed as completed on Oct 23, 2026. The fix is in the source; check the changelog for the build that carries it.
- Cross-gateway rooms are text-only. RoomLink does not carry attachments.
- The iPhone does not courier room traffic in the background.
- Cross-gateway @Bot DM relay is not guaranteed by Fleet.
- Promotion of a room replica does not fence the previous authority.
- Fleet Home coverage is bounded. There is no fleet-wide telemetry, and unknown is shown as unknown.
- Features depend on the connected gateway’s version. Unsupported capabilities stay unavailable.
- Approval responses are not cryptographically signed yet.
Found something not listed? Report a bug; the form checks your report for credentials, private addresses, and other details that shouldn’t be public.