WHAT DOESN'T WORK

Known issues

Last updated: August 29, 2026

What doesn't work right now, and what to do instead.

We would rather tell you than have you find out. Every entry is dated, and we take them down when they stop being true.

A free room that reaches a limit blocks recovery too

Posted 2026-08-29

A free room is metered. When it reaches one of its bounds, the limit is applied to the whole connection before any tool runs — so reading and removing memories are refused along with writing them. That is the part we consider a bug rather than a limit: at the moment you most need to look at what is in a room, or clear something out of it, you cannot.

There are two bounds and they do not behave the same way. The daily operation budget clears by itself at midnight UTC, and a search counts against it because it embeds. Total capacity does not clear by itself, because the one action that would free space is blocked by the same gate.

The message the server returns today suggests running the open-source server instead. That is not a recovery path for a room you already have — it is a different install, and it will not bring back what is in the room. If this happens to yours, mail us at the address below before you do anything else; the room is intact, it is the door that is shut. We are working on letting recovery through while writes stay blocked.

Recently resolved

Posted 2026-08-15 · Resolved 2026-08-23

Claude on the web couldn't open a One Night room. The original entry said this wasn't something we could fix by changing a setting on our side. That turned out to be wrong: a bot-protection default on our edge was rejecting the connection before it reached us. We turned it off, watched Claude on the web open a room, and took the entry down. Rooms now work from every client we list.

Found something else?

Tell us: support@living-memory.app — including the boring things. If it turns out to be ours, it goes on this page with a date.

Living Memory · this page is maintained by hand, not generated. If an entry is stale, that's a bug too.