Skip to main content
Use ana org to upload, organize, and share your packages on Anaconda.org from the Anaconda CLI.

How ana org relates to anaconda-client

ana org runs anaconda-client, the tool that provides the anaconda command. Anaconda CLI installs and manages its own copy of anaconda-client, separate from your conda environments, so you don’t need to install it yourself. If that copy isn’t installed yet, ana installs it the first time you run an ana org command. When you update ana, its copy of anaconda-client updates too. Each ana org command does the same thing as the anaconda command with the same name. For example, ana org upload is equivalent to anaconda upload, and ana org channel create is equivalent to anaconda channel create. If you already use anaconda-client from a conda environment (Anaconda Distribution includes it), your existing anaconda commands continue to work. Because ana org runs anaconda-client, messages from these commands refer to anaconda commands. For example, an error might suggest running anaconda --verbose org upload or anaconda remove. To follow a suggestion like this with the Anaconda CLI, run the same command with ana org in place of anaconda or anaconda org.
The Anaconda CLI version 1.0.1 and later include anaconda-client 1.15.0. Options added in later versions of anaconda-client are not available through ana org until a new Anaconda CLI release includes them.

Logging in

ana org commands use two kinds of credentials:
  • Anaconda account API key: Every ana org command requires you to be logged in with ana login. If you aren’t, ana prompts you to log in before running the command. The ana org channel commands for private channels use this API key.
  • Anaconda.org token: Commands that act on your Anaconda.org account, such as upload, copy, move, label, remove, auth, and channel notice, also require an Anaconda.org token. ana org login creates this token from your saved API key, without asking you to sign in again.
To set up both credentials, run:
If you run a command that needs an Anaconda.org token before you’ve created one, the command creates the token for you when you run it in an interactive terminal. In scripts and other non-interactive sessions, the command fails with an Unauthorized (401) error instead, so run ana org login beforehand or set the ANACONDA_API_TOKEN environment variable. To see who you’re logged in as, run ana whoami for your Anaconda account or ana org whoami for Anaconda.org. If you haven’t created an Anaconda.org token, ana org whoami displays Anonymous User.
In CI/CD pipelines, store an Anaconda API key and an Anaconda.org token in your CI provider’s secret storage. Log in to ana with the API key first, and then set ANACONDA_API_TOKEN to the Anaconda.org token so that ana org commands don’t need ana org login. For example, if your pipeline exposes the secrets as ANACONDA_API_KEY and ANACONDA_ORG_TOKEN:
Without the ana login step, ana waits for a browser login that no one can complete. For more information about logging in with an API key, see Non-interactive login for CI/CD. To create an Anaconda.org token, see ana org auth.

Commands

Concepts

Labels
Labels are used to organize package versions within an account. The default label is main. Use the label command to list, copy, lock, unlock, and remove labels.
Package spec
Many commands accept a package spec in the format USER[/PACKAGE[/VERSION[/FILE]]]. Each level of the spec narrows the scope of the operation, from user to package, version, or specific file.
Channels
Channels are package repositories that users can install from. Use the channel command to create, list, and manage channels. Channel administrators can also create notices to display messages to users when they install or update packages.
Anaconda.org
The Anaconda repository at anaconda.org where packages are hosted. anaconda-client communicates with the Anaconda.org API to manage packages, users, and tokens.

Global options