almanac is not found
Find uv’s executable directory, update PATH for future terminals, and ensure the
latest Almanac version is installed:
almanac executable from the directory printed
by the first command. See Install the CLI.
The CLI asks you to sign in
Runalmanac login. For automation, confirm ALMANAC_TOKEN contains the actual
waka_... secret rather than an API key ID or obfuscated value. Secrets are shown
only once.
No Organization is selected
Runalmanac whoami, then either link the project or pass an explicit
Organization ID or slug:
An upload remains processing
Keep theupload ID printed by the command and check the source library with
almanac sources tree. Include the upload ID and any request_id when
reporting a problem. See Upload sources.
Search returns no results
Queries need at least two letters or numbers. Verify the selected Organization, then browsealmanac pages list and almanac sources tree to separate a
page-generation problem from a missing-source problem.
An agent cannot access Almanac
Confirm the agent can runalmanac whoami, then run almanac setup to reinstall
the current guidance. Almanac does not expose a separate agent connection
surface; agents use the same CLI.