Skip to main content
Use the CLI when Almanac needs local files, a person is working interactively, or a coding agent can run terminal commands.

​
The everyday loop

The link gives the directory durable context. Upload adds original evidence; sources, search, and show verify the resulting knowledge.

​
Use connected provider tools

accounts list prints the safe Account IDs, labels and ownership available to the current Almanac, even when an Account’s provider has no tools yet. The same provider.tool shape extends to future providers. Almanac selects the only eligible Account automatically and asks for --account only when more than one can run the tool.

​
Connect and manage Accounts

Choose --personal or --shared explicitly when connecting. The CLI opens the provider handoff in your browser and waits for the Account to connect. In a remote terminal, use --no-open to print the URL; add --no-wait when another process will check the result later. JSON output never includes the provider credential or Nango connect-session token. Account management requires your saved browser login. Inside a member Quill, pass global --user; shared Quills and automation keys cannot manage Accounts. remove stops using a personal Account in only the selected Organization. disconnect --yes revokes the Account everywhere, while existing Wiki content remains.

​
Make the target explicit

An explicit --organization overrides the environment, directory link, and signed-in default. See Link an Organization for the selection model.

​
Authenticate a program

Use browser login for people and CLI automation keys for programs. A token supplied with --token or ALMANAC_TOKEN does not replace the saved browser login.

Automate the CLI

Use serialized writes, JSON output, and exit codes.

Open the CLI reference

Scan commands by task and discover help.