-
jackmc joined the community
-
[Support] NanoClaw — Lightweight Secure AI Agent for Unraid
Hi BitCryptic, thanks for the project and the template work. I've hit a wall getting NanoClaw responding on Matrix and have done a fair bit of diagnostic work. Hoping you can spot what's wrong — happy to provide anything else useful. Setup NanoClaw v1.3.0 (image: bitcryptic/nanoclaw:latest, container ID 4fd55fe1a417) Installed via Community Apps on Unraid Matrix-only (no Telegram configured) Auth via CLAUDE_CODE_OAUTH_TOKEN (no ANTHROPIC_API_KEY set) NANOCLAW_DOCKER_NETWORK=ai-local (network exists and is reachable) AppData at /mnt/cache/appdata/nanoclaw/ Default trigger @Andy, bot user @nectaron-andy:matrix.org, homeserver matrix.org What works Container starts cleanly, no errors Matrix invites auto-accept Crypto store bootstraps, cross-signing keys imported, device verifies, key backup activates Incoming messages decrypt successfully — logs show Decrypted event received with the correct room ID and event ID chats table in messages.db populates with each new room What doesn't work After Decrypted event received, nothing happens. No registration, no trigger evaluation, no agent spawn, no error. Just sync polling resumes. registered_groups table is empty across all attempts messages table is empty — incoming messages are never persisted /mnt/cache/appdata/nanoclaw/logs/ is empty /mnt/cache/appdata/nanoclaw/groups/ is empty docker ps -a shows only the main NanoClaw container — no agent containers have ever been spawned Agent images are present locally (nanoclaw-agent:latest, nanoclaw-agent-v2-<hash>:latest), so no image build issue Things I've tested Multiple fresh DM rooms (6+) — chat appears in chats table, no registration follows Trigger as first chars of message: @Andy hello (plain text, mention pill removed) NANOCLAW_REQUIRE_TRIGGER=false Fresh MATRIX_ACCESS_TOKEN regenerated via password login Wiped /mnt/cache/appdata/nanoclaw/data/matrix-crypto-store/ and restarted to fix initial E2E key issues (this worked — decryption is now clean) Confirmed ai-local Docker network exists Confirmed Docker socket is mounted Filtered NanoClaw-only log output around a fresh message arrival [12:10:11.462] INFO (1): Matrix invite auto-accepted roomId: "!xsopKMBPbJldMQcWYc:matrix.org" [12:10:13.188] INFO (1): Decrypted event received eventId: "$UriIj45vGFeFS55aiJF8ulZZpi3lkbYbjv27lmKXauY" type: "m.room.message" encrypted: true roomId: "!xsopKMBPbJldMQcWYc:matrix.org"…then silence apart from sync polls and periodic crypto-store persistence. No application-level logging beyond this point. Database state after sending several messages across rooms sql SELECT * FROM chats; -- 6 rows, all matrix rooms, populated correctly SELECT * FROM registered_groups; -- empty SELECT * FROM messages; -- emptyIt looks to me like the message handler is receiving and decrypting events fine, but the path from "event decrypted" → "store message + register group + invoke agent" isn't connected (or is silently bailing very early) on this install. Could it be related to the Matrix-only setup, the OAuth token vs API key auth, or something about how the crypto store wipe + cross-signing import interacts with the registration flow? Happy to share the full docker logs, container template (with secrets redacted), or run any further commands. Thanks for taking a look.
jackmc
Members
-
Joined
-
Last visited