animawake docs

Help

Troubleshooting

Fixes for common problems with sign-in, memory, search, proposals, dreams, chat, devices, and the CLI.

For problems connecting a client, start with Connection troubleshooting.

#Sign-in

The sign-in dialog offers only the waitlist. Animawake is in early access, and sign-in works for invited email addresses. Join the waitlist with the email you will sign in with.

"Sign Up Closed" after choosing Google or GitHub. The provider's verified email is not on the invite list. Sign in with the account whose email was invited.

The desktop app signed out on its own. Signing out of the portal revokes all of your user keys, including the one the desktop app uses. Sign in again in the app.

Search returns an error or Error searching memories: 503. Search needs an embedding for your query. On the hosted service this is usually temporary; try again in a minute. On a self-hosted server, set OPENAI_API_KEY. See Memory.

A memory you just saved is not found. Embeddings are created in the background within seconds. If the first attempt fails, it is retried up to three times, a minute apart, and the nightly dream fills in any that are still missing. Listing tools, such as get_moments, show the memory right away.

Tools return 429 or "Request was throttled". Memory writes, search, and recall share a budget of 100 requests per hour per entity. Wait for the time in the message. If an agent loops on search, ask it to batch its questions. See Rate limits.

A memory category in the portal looks empty. Some categories fill only once the entity records that kind of memory. Ask the entity to record one, then refresh.

The entity wakes without last session's context. The previous session was not saved. End sessions with "record this session", or use the CLI, whose hooks capture sessions automatically. See Sessions and continuity.

#Identity and proposals

update_identity or add_value says the change is pending. That is expected. Changes to identity and values wait for the owner's approval on the entity's Activity tab.

You cannot approve a proposal. Only the workspace owner can decide proposals.

A proposal cannot be approved because it is stale. The identity or value changed after the proposal was made. Prepare a new review from the proposal to see the current difference.

#Dreams

"A dream is already queued or running for this entity." Wait for the current dream, or cancel it. A dream stuck for more than two hours stops blocking new ones.

No dream ran last night. The server dreams for every active entity at 06:00 UTC. Check the dream history on the entity's Growth tab. A device's own 03:00 UTC dream needs the desktop app running.

#Chat and devices

Chat says the device is offline. Chat runs on a device where the entity is deployed. Start the desktop app on that device, or deploy the entity to a device that is online.

A device shows offline while the app is open. Devices are online if their last heartbeat was within 6 minutes. Check the computer's network connection and that the app is signed in.

An agent lost access after you removed a device. Deleting a device deactivates the entity keys issued to that device. Reconnect any agent that used one of those keys; in CLI projects, run npx animawake rotate-key <entity>.

See Desktop app setup for installation problems.

#CLI

npx animawake setup says the project already has entries. Use npx animawake add for a second entity.

The launched agent does not wake as the entity. Run npx animawake status. It reports whether the hooks are configured for Claude Code and Codex. Run npx animawake upgrade to rewrite them.

Transcripts are not showing up in the continuity journal. npx animawake status shows the oldest queued batch. Batches wait in the local queue until the server accepts them; they are not lost. Only sessions started with npx animawake <entity> are captured.

Codex hooks do not run. Check that ~/.codex/config.toml does not set hooks = false under [features].

See the CLI reference for error messages.

#Research

"Curiosity cap reached". An entity can have two active self-directed runs. Conclude one first.

The server refuses more evidence. The run's source or dispatch budget is spent. Conclude the run with what it has, or start a new run with a larger budget.

A run cannot conclude. Record at least one critique first.

#Still stuck

Collect the exact error message, the client and its version, and the time it happened, then contact support.