Troubleshooting

The common bumps, and what to do about each.

Signing in

"No browser wallet found"

Your wallet is locked, or the page loaded before it was ready. Click the wallet's icon in your toolbar, unlock it, and reload the page. Still nothing? Check the extension is switched on in your browser's extensions page.

"This wallet is not the admin wallet for this server"

The account your wallet is using isn't the one the server was set up with. Switch accounts in your wallet and try again. If you've only ever had one, ask whoever set up the server which address they used.

"You cancelled in the wallet"

Nothing happened, and nothing changed. Click the button again when you're ready.

I'm on my phone

The admin page needs a wallet browser extension, so use a computer. Claude itself works on your phone once it's connected.

Claude and memory

The admin page says no policy is approved

Memory stays off until you approve one. See Your first policy.

Claude doesn't seem to use its memory

Check AIngram is switched on in the chat's connectors or tools menu, and that Claude has the instructions. You can always nudge it: "Check AIngram before you answer."

A chat seems stuck, or AIngram stops answering

Claude's connection renews itself every 7 days. If a chat gets stuck right after that, start a new chat. If it still fails, check the connection is still listed under Keys on the admin page; if it was revoked, connect again.

Claude says it can't connect at all

Check the connector's address ends in /mcp and matches the one on the admin page's Overview. If the admin page itself won't load, the server may be down; tell whoever runs it.

Claude says it has reached its daily limit

Each voice can write a set number of notes a day: 300 for the brain and 60 for Code by default. It resets the next day, or you can raise it in your policy. Reading is never limited.

Claude Code can't write to a project

Code may only write under the project folders listed in your policy. Add the project's folder there, and approve it again.

Importing

The preview shows problems

Each problem names its line. Tell Claude which line and what the problem says, and ask for a corrected file. Nothing is written until the whole file passes and you sign.

For the server's administrator

Memory switched off after an update

The approved policy is missing a setting the new version needs, so the server played safe. The admin page shows the problem and opens the policy for fixing; approve the fixed version and memory comes back on.

Memory switched off after changing settings

Changing the admin address or the web address means earlier approvals no longer apply. Sign in with the admin wallet and approve the policy again.

The service won't start

sudo journalctl -u aingram -n 50 shows why. The most common causes are a missing setting in /etc/aingram/aingram.env, or the database folder belonging to the wrong user.