"… presented key …, not the paired one: nothing was sent": the server the bridge reached doesn't hold the key you pinned. Check the address, then compare the safety code shown under Settings › Agents › New token. The key changes only when the server's data folder lost its tls/ key; then every phone has to pair again too.
"No terminal to confirm the safety code on": the bridge was run with no --pin and no --safety-code. Add --pin with the fingerprint to the configuration.
"FILAMAMA_TOKEN is not set": the token goes in the env block of the configuration (or -e for Claude Code), not in the arguments.
"Token refused: revoked, expired, or not an agent token": the token was revoked or has expired, its account is disabled, or it was pasted wrong. Make a new one.
"This token may not write to the library": the assistant tried a write with a read-only token.
"Rate limited; retry after N s": too many calls in a minute. The assistant can go on after the wait; nothing was lost.
"The server could not be reached": the computer isn't on the home network, the address or port is wrong, or the server is off. Opening the web app in a browser on the same computer is the test.
Node errors on start (SyntaxError, node: command not found): the bridge needs Node.js 20 or newer. Check with node --version.
No tools at all: the server was started with DMS_MCP=off, or the assistant hasn't been restarted since the configuration changed.