Get back to the useful part.

The shell cannot find serenity

Check the installation completed, then check PATH. Source installs use go env GOBIN, or the bin directory under GOPATH when GOBIN is empty. Open a fresh shell after changing PATH.

Initialization fails at the keychain

Initialization requires an accessible OS keychain. On a headless or locked session, verify that your keychain service is available and unlocked. Do not work around this by storing the authentication token in a public repository.

Search finds nothing

1. Confirm -C points to the intended brain.
2. Check the absolute connectors.file.path in that brain’s configuration.
3. Allow files to remain unchanged for at least two seconds.
4. Run serenity sync, then serenity status.
5. Search for a distinctive phrase that is actually in a source.

Ask or extraction is disabled

New brains start with none@v0 model pins. Configure extraction and composition, provide credentials in the process environment, and run extract after sync. See model setup.

Gmail authentication stopped working

Re-run serenity connectors auth imap --email you@gmail.com with a valid app password. Confirm 2-Step Verification and app-password availability on your account. The connector is certified for Gmail app passwords, not OAuth.

A documented command is missing

Packaged v0.1.1 predates newer source workflows. Check serenity --help and use the current-source installation if you need the guides on this site.

Report a reproducible problem

Include your platform, install method, command, and a small sanitized example. Remove private notes, credentials, and account information before posting.