Skip to main content
Automation should make authentication and wiki scope explicit:
export ALMANAC_TOKEN="waka_..."
export ALMANAC_WIKI="acme/company-handbook"

Request JSON

almanac search "customer onboarding" --json
--json writes one JSON value to standard output and suppresses the human scope banner. The JSON includes the resolved wiki and scope where relevant.

Serialize CLI writes

The CLI upload result says whether a job was queued but does not expose its ID. last is therefore safe only when your automation serializes writes to the wiki and waits immediately:
almanac upload docs/ --json
almanac jobs wait last --json
Duplicate-only uploads return no new job. Handle that branch instead of waiting for the previous last job. When concurrent writers need an exact job ID, use the Python SDK or REST API, whose upload responses include the nullable job record.

Exit behavior

Exit codeMeaning
0Command completed successfully
1Almanac reported an error
2Command syntax or arguments were invalid
130Command was interrupted
Run almanac COMMAND --help for command-specific flags. See CLI reference for the command map and API keys for least-privilege permissions.