BeavBeav

Docs

Frequently asked questions

Quickly locate common problems with installation, the browser extension, the knowledge base, Agent connections, and media tasks.

The desktop app will not open

Check that the package matches your operating system and architecture. macOS on Apple Silicon uses aarch64 and Intel uses x64; most Windows and Linux machines use x64. On Linux, prefer the AppImage, while Debian, Ubuntu, and derivatives can also use DEB. Before re-downloading, confirm whether the original file is complete.

The browser extension will not connect

Keep Beav running, confirm the extension is enabled, reload the extension, and refresh the page. Full steps: Browser extension troubleshooting.

The saved content cannot be found

Check the current workspace and the knowledge base filters. Search by the source title or link, and look at the extension's task history. If it reports a partial success, follow the error: wait for the page to finish loading, or capture once more.

The Agent read the website but did not connect to Beav

First confirm the Agent runs on the same computer as Beav. A web or cloud Agent cannot read the local discovery file. Then check that the ACP Gateway is enabled, Beav is running, and the token is provided through an environment variable.

The Agent starts a new session every time

Ask the Agent to save and reuse the sessionId or acpSessionId from the previous response. Do not drop the session ID while continuing the same creation goal.

A media task runs for a long time

Check the task status and events first, and do not resubmit the same generation. If it hits awaiting_approval, handle the approval. Details: Performance and long tasks.

The result appeared, but the project does not contain it

Check whether the result was saved into the media library and bound to the right draft, subject, or project. A temporary preview or a link in chat is not a proper asset record.