# Anaconda Desktop Source: https://anaconda.com/docs/anaconda-desktop/key-features Anaconda Desktop provides a comprehensive solution for both AI development and data science workflow management. Download and interact with powerful Large Language Models (LLMs) directly on your computer, while also managing your development environments, packages, and applications through an intuitive graphical interface. For AI developers, Desktop includes a built-in llama.cpp API server and access to Anaconda's curated index of trusted models. For data scientists and Python developers, Desktop simplifies environment management, package installation, and application launching. ## Key features ### Development workflow management * **Environment Management**: Create conda environments configured with the Python version you need, and manage packages and dependencies through a graphical interface that keeps projects isolated and reproducible. * **Application Catalog**: Install and launch popular data science applications like JupyterLab, Spyder, and Jupyter Notebook directly from Desktop, with automatic environment setup and dependency management. * **Visual Package Management**: Install, update, and remove packages through an intuitive interface that shows dependency relationships and manages compatibility automatically. * **Channel Configuration**: Control package sources and repositories to ensure you're using trusted, approved packages for your organization or projects. ### AI model management and interaction * **Local Model Deployment**: Download and run powerful LLMs directly on your computer without requiring external servers, maintaining complete control over your data and privacy. * **Curated Model Repository**: Access a comprehensive catalog of open-source models with performance benchmarks and multiple quantization options. * **Real-time Chat Interface**: Chat directly with downloaded models using customizable parameters to evaluate performance and fine-tune behavior. * **API Server**: Provides RESTful endpoints for local model inference with authentication and monitoring features, enabling developers to thoroughly test and evaluate models with applications they are developing. * **Visual Model Comparison**: Compare models based on performance benchmarks, file size, and memory requirements with interactive charts. ### Enterprise management and control * **Anaconda Platform Integration**: Enterprise customers can use Anaconda Platform to control which models their users can access within Anaconda Desktop, ensuring compliance with organizational policies and security requirements. * **Secure Local Deployment**: Maintain data privacy and security while providing controlled access to AI capabilities across your organization. # Managing your account Source: https://anaconda.com/docs/anaconda-org/accounts Anaconda accounts are shared across all Anaconda products, including Anaconda.org and Anaconda.com. You don't need an account to search for public packages on Anaconda.org, but an account enables you to do the following: * Author and manage packages * Upload packages * Create organizations This page contains information on creating and managing an Anaconda account in Anaconda.org. ## Creating an account To sign up for an Anaconda account: 1. On Anaconda.org, click **Sign up**. 2. From here, you can sign up via a Google, Microsoft, or GitHub account, or select **Sign Up with Email** and enter an email and password. 3. If you chose **Sign Up with Email**, verify your account using the email sent to your email address. 4. Enter your name and optional information about yourself. 5. Create a username and click **Save Username**. > [!TIP] > > Anaconda.org displays your profile photo if the email address you used to register on Anaconda.org is associated with a Gravatar account. To associate your email address or change your Gravatar profile photo, go to [gravatar.com](https://gravatar.com/). ## Signing in You have several ways you can sign in to Anaconda.org, depending on your setup: **Browser sign-in** 1. On [Anaconda.org](https://anaconda.org), click **Sign In**. 2. Sign in using any of the following: * your Anaconda.org username and password * your Anaconda account credentials * a linked Google, Microsoft, or GitHub account > [!NOTE] > > Enterprise Single Sign-On or Single Sign-On (ESSO/SSO) users should enter their email address and click **Sign In** to use single sign-on. **Terminal** 1. Sign in to Anaconda.org using the following command: ```sh theme={null} anaconda login --at anaconda.org ``` 2. On the browser page that appears, sign in using any of the following: * your Anaconda.org username and password * your Anaconda account credentials * a linked Google, Microsoft, or GitHub account > [!NOTE] > > Enterprise Single Sign-On or Single Sign-On (ESSO/SSO) users should enter their email address and click **Sign In** to use single sign-on. **CI/CD flows** CI/CD or other non-interactive flows should sign in to Anaconda.org using [tokens](/docs/anaconda-org/admin-guide/tokens). ## Viewing your user profile To view your user profile: 1. Log in to Anaconda.org. 2. Click the user dropdown menu. 3. Select *Profile*. > [!TIP] > > You can also view your user profile by navigating to `https://anaconda.org/users/`. Your user profile displays general profile information, including your username and email address. It also displays any organizations you are a member of and any packages you have uploaded to your account. ## Updating your user profile To update your user profile: 1. Log in to Anaconda.org. 2. Click the user dropdown menu. 3. Select *Settings*. 4. On the **Public Profile** page, update your profile information. 5. Click *Update Profile*. ## Resetting your password To reset your password: 1. Log in to Anaconda.org. 2. Click the user dropdown menu. 3. Select *Settings*. 4. Select **My Account** in the left-hand menu. Verify your password, if prompted. 5. In the **Change Password** section, enter your old password, then enter and confirm a new password. 6. Click **Change Password**. ## Upgrading or downgrading your plan If you require more private packages or storage space than is included in a personal plan, [contact Anaconda](https://www.anaconda.com/contact) so we can customize a plan for you. ## Troubleshooting Troubleshoot ### Captcha not appearing when trying to create an Anaconda.org account on Firefox ***
Cause The captcha at the bottom of the **Sign In** panel on [Anaconda.org](https://anaconda.org/) sometimes fails to appear on Firefox browsers. The captcha might be blocked by an ad blocker extension, tracking blocker extension, or Firefox's privacy settings.\ \\ ![](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-org/firefox-missing-captcha.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=4751404f8d50600178b6f34b07119246)
***
Solution 1. Refresh your browser and try again. If refreshing multiple times, wait a few seconds between each refresh. 2. Check your extensions. Extensions that block tracking or ads might also block the captcha. 3. Check your browser settings. Privacy settings might block the captcha. 4. Open the [sign in page](https://anaconda.org/) in a [private browsing window](https://www.mozilla.org/en-US/firefox/features/private-browsing/).
Troubleshoot ### "URI no longer exists and has been permanently removed" 410 error when attempting to upload notebooks or environments to Anaconda.org ***
Cause The Notebooks and Environments features have been removed from Anaconda.org as part of an initiative to streamline and improve Anaconda.org and enable the site to focus on package hosting and management. Because of this, notebook and environment files can no longer be uploaded to Anaconda.org using the `anaconda upload` command.
***
Solution Although you can no longer upload notebooks to Anaconda.org, you can share your notebooks with others using [Anaconda Notebooks](https://nb.anaconda.com) instead. Anaconda Notebooks come with their own preloaded Environments and allow you to create your own custom environments as well. For more information on sharing notebooks with Anaconda Notebooks, see [Sharing notebooks](/docs/anaconda-platform/notebooks/sharing-notebooks).
Troubleshoot ### Users don't have passwords for `anaconda-client` login to Anaconda.org ***
Cause If you created an account on Anaconda.org and used the Google, Microsoft, or GitHub authorization options to sign up, you do not have a password associated with your account. `anaconda-client` v1.13.1 and older require a username and password to log in to anaconda.org.
***
Solution To log in to anaconda.org without a password using `anaconda-client`, you must update `anaconda-client` to v1.14.0 or later in your base environment: 1. Open Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux). 2. Update or install `anaconda-client` by running the following command: ```sh theme={null} conda install --name base "anaconda-client>=1.14.0" ``` 3. Log into Anaconda.org: ```sh theme={null} anaconda org login ``` 4. A browser window opens to authenticate you to Anaconda.org. Sign in with your account credentials to complete authentication in the browser.
# Groups Source: https://anaconda.com/docs/anaconda-org/admin-guide/groups Groups are an effective way to organize users and control access to your packages on Anaconda.org. Group owners have administrator level permissions over the group and can manage member permissions for all other individuals in the group. ## Creating groups You can create a group to customize access for a group of users. View your existing groups by clicking your profile in the top-right corner and selecting **Groups** in the dropdown. To create a group: 1. From your profile in the top-right corner, switch to an organization you have created by selecting **Switch to…**. 2. From your profile, select **Groups**. 3. Click **New Group**. > [!NOTE] > > If **New Group** is not present on this page, you might be in your default profile rather than in an organization. If the title of this **Groups** page reads "group membership" rather than "groups", you need to switch to an organization. If you do not have an organization, [create one now](/docs/anaconda-org/admin-guide/organizations). 4. Give the group a name without any spaces, then click **Create group**. ## Customizing users and groups To add, remove, or edit group and user access for an organization you administer: 1. From your profile in the top-right corner, select the preferred organization profile under **Switch to…**. 2. From your profile, select **Groups**. 3. Select the group you want to customize. From this group page, you can: * Add and delete group members * Change the group name * Adjust permissions for group members * Delete the group * Add and delete packages ### Adding group members 1. Navigate to the **Group** page at `https://anaconda.org//groups/`, where `` is the organization name and `` is the group name. 2. Under **Members**, enter a member's username, then click **Add**. > [!NOTE] > > Users receive a dashboard notification on Anaconda.org when you add them to an organization. ### Changing a group name 1. Navigate to the **Group** page at `https://anaconda.org//groups/`, where `` is the organization name and `` is the group name. 2. Select **Settings**. 3. Under **Name**, enter a new group name, then click **Save**. ### Adjusting group member permissions 1. Navigate to the **Group** page at `https://anaconda.org//groups/`, where `` is the organization name and `` is the group name. 2. Select **Settings**. 3. Under **Permissions**, select your preferred permission level, then click **Save**. There are three types of permissions you can grant: * **Read Only**: Provides access only to the packages. Users in a read-only group can see the list of files within a package and can install them through conda. * **Read-Write**: Provides access to upload new versions of an existing package, delete files of a package, and manage the individual labels of files. Users in a read-write group cannot upload files for non-existing packages, delete or transfer the package, or lock/unlock labels. * **Administration**: Provides access to everything except uploading new packages (admin users can still upload to an existing package) and locking/unlocking labels. ### Deleting a group 1. Navigate to the **Group** page at `https://anaconda.org//groups/`, where `` is the organization name and `` is the group name. 2. Select **Settings**. 3. At the bottom of the page, click **Remove Group**. ### Adding packages 1. Navigate to the **Group** page at `https://anaconda.org//groups/`, where `` is the organization name and `` is the group name. 2. Select **Packages**. 3. Enter the name of the package you want to add in the **Package name** cell, then click **Add**. If you want to add all of the packages in the organization to your group, click **Add all Packages**. # Channel notices Source: https://anaconda.com/docs/anaconda-org/admin-guide/notices Channel notices allow channel administrators to communicate important information to users who install packages from their channel. When users run `conda install` or `conda update` from a channel with active notices, conda displays these messages in the terminal. Use channel notices to announce: * Breaking changes in upcoming releases * Deprecation warnings * Security advisories * Migration instructions * Maintenance windows For more information on `anaconda channel notice` command options, see [`anaconda channel notice`](/docs/cli-reference/anaconda-client/commands/channel-notice). ## How notices work When you publish a notice to your channel, conda clients automatically fetch and display it to users during package operations. Each notice has a unique ID, and once a user has seen a notice, it won't be shown again. Conda fetches notices from `https://conda.anaconda.org//notices.json`. Users must have the channel configured in their `.condarc` file to receive notices. ## Notice lifecycle Notices follow a three-stage lifecycle: 1. **Draft**: Created but not visible to channel users. Use drafts to prepare notices before publishing. 2. **Published**: Active and visible to channel users until the expiration date. 3. **Archived**/**Deleted**: No longer visible to users. Archive notices to stop showing them before their expiration date or to preserve them for records. Delete records to remove them from the notice list. > [!NOTE] > > Archived notices can be restored by applying the `publish` status to them again. Deleted notices can still be viewed with `anaconda channel list` by specifying `--status deleted`, but cannot be restored. ## Prerequisites * [anaconda-client](/docs/cli-reference/anaconda-client/getting-started) version 1.15.0 or later * Owner or administrator access to the channel To verify your anaconda-client version: ```sh theme={null} anaconda --version ``` To update your anaconda-client version: ```sh theme={null} conda install --name base anaconda-client=1.15.0 ``` ## Creating a notice Create a notice with the `anaconda channel notice create` command. > [!NOTE] > > Notices are created as drafts by default and must belong to a specific channel, even if you are not publishing them yet. ```sh theme={null} anaconda channel notice create --message "" --level --expires-after ``` Comments Replace \ with your channel name (your username or organization name).\\ Replace \ with your notice text (max 600 characters).\\ Replace \ with the severity level for your message.\\ Replace \ with the number of days until the notice expires. ### Options Option Description `--message ` The notice text to display (max 600 characters). Can include a URL. `--level ` Notice severity: `info` (default) for general announcements, `warning` for deprecations or breaking changes, `critical` for security issues or urgent actions `--expires-at ` Expiration date in ISO 8601 format (for example, `2026-12-31T00:00:00Z`) `--expires-after ` Number of days until expiration (minimum 1, alternative to `--expires-at`) `-n, --namespace ` Channel owner (user or organization). Alternative to the positional `` argument. ### Example Create a warning notice that expires in 30 days: ```sh theme={null} anaconda channel notice create my-channel --message "Version 2.0 removes deprecated API. Migrate by Jan 2027." --level warning --expires-after 30 ``` If you omit `--message` or expiration options, the CLI prompts you interactively (with a default expiration of 30 days). After creation, the CLI displays the notice ID and a hint showing how to list notices. You're then prompted to publish immediately—if you decline, the notice remains in draft status. ## Finding a notice ID When you create a notice, the command outputs the notice ID (a UUID). If you didn't save it, use `list` to find it. Use `--status` to filter by `draft`, `published`, `archived`, or `deleted`. ```sh Command theme={null} anaconda channel notice list --status ``` ```sh Example theme={null} anaconda channel notice list my-channel --status published ``` The output displays a table with each notice's ID, status, level, message, and expiration date. Copy the ID from the **Notice ID** column to use with other commands like `get`, `update`, `publish`, `archive`, or `delete`. ### Pagination For channels with many notices, use pagination to limit the number of notices you are seeing: * `--offset` — Number of notices to skip (default: 0) * `--limit` — Maximum notices to return (default: 20) ```sh theme={null} anaconda channel notice list my-channel --offset 5 --limit 10 ``` ## Publishing a notice To make a draft or archived notice visible to channel users, use the `publish` command. Use the `--force` flag to skip the confirmation prompt. ```sh Command theme={null} anaconda channel notice publish [--force] ``` ```sh Example theme={null} anaconda channel notice publish my-channel 128cd00e-c58f-407f-aab2-ea39159e3cf3 --force ``` ## Getting notice details View the full details of a specific notice, including status, level, message, expiration date, and timestamps. ```sh Command theme={null} anaconda channel notice get ``` ```sh Example theme={null} anaconda channel notice get my-channel 128cd00e-c58f-407f-aab2-ea39159e3cf3 ``` ## Updating a notice Modify an existing notice's message, level, status, or expiration. If you do not add all required information to the initial command, you will be prompted for each piece of information. ```sh Command theme={null} anaconda channel notice update --message --level --expires-after ``` ```sh Example theme={null} anaconda channel notice update my-channel 128cd00e-c58f-407f-aab2-ea39159e3cf3 --message "Updated migration deadline: Feb 2027" ``` ## Archiving a notice Archive a notice to stop showing it to users before its expiration date. Archived notices can be republished later using the `publish` command. Use the `--force` flag to skip the confirmation prompt. ```sh Command theme={null} anaconda channel notice archive [--force] ``` ```sh Example theme={null} anaconda channel notice archive my-channel 128cd00e-c58f-407f-aab2-ea39159e3cf3 --force ``` ## Deleting a notice Delete a notice to remove it from the default notice list. Deleted notices can still be viewed with `--status deleted` but cannot be restored. ```sh Command theme={null} anaconda channel notice delete [--force] ``` ```sh Example theme={null} anaconda channel notice delete my-channel 128cd00e-c58f-407f-aab2-ea39159e3cf3 --force ``` > [!CAUTION] > > Deleted notices cannot be restored. Consider archiving notices instead if you might need to republish them later. ## Organization channels For organization channels, use the `--namespace` or `-n` flag to specify the organization. You must be an owner or administrator of the organization to manage its channel notices. ```sh Command theme={null} anaconda channel notice --namespace ``` ```sh Example theme={null} anaconda channel notice list --namespace my-org --status published ``` ## Best practices * **Keep messages concise**: Use clear, actionable messages. Include a URL for additional details. * **Set appropriate expiration dates**: Choose expiration dates that give users enough time to see and act on the notice. * **Use meaningful notice levels**: Reserve `critical` for genuinely urgent issues to avoid alert fatigue. * **Test with drafts**: Create notices as drafts first, review them, and then publish when ready. * **Archive instead of delete**: Archive old notices for record-keeping rather than deleting them permanently. # Organizations Source: https://anaconda.com/docs/anaconda-org/admin-guide/organizations Organizations in Anaconda.org help you manage package access and collaboration through group-based permissions. When you create an organization, a dedicated channel is also created for storing and distributing your organization's packages. Control who can access the channel by adding users to the channel's [group](/docs/anaconda-org/admin-guide/groups). Organizations also serve as the namespace for [private channels](/docs/anaconda-org/private-channels), which let you distribute packages to specific collaborators. > [!TIP] > > View an organization's channel by navigating to `anaconda.org/channels/`, where `` is the name of the organization. ## Creating an organization As the creator and owner of an organization, you have automatic administrative access to this organization and any packages associated with the organization. You can view your organizations by clicking your profile in the top-right corner and selecting **Profile** in the dropdown. To create an organization: 1. Log in to Anaconda.org. 2. From your profile in the top-right corner, select **New Organization**, and then scroll to the bottom of the page. 3. Enter an organization name. > [!NOTE] > > Organization names cannot include spaces or special characters. 4. Enter an email address, then click **Create Organization**. The system displays the dashboard for the new organization. ## Deleting an organization To delete an organization you administer and erase all data associated with it: 1. From your profile in the top-right corner, select **Switch to…**. 2. Select the organization you want to delete. 3. From your profile, select **Settings**. 4. Select **My Account** in the left-hand menu. You might be asked to verify your password. 5. In the **Delete Account** section, click **Delete**. 6. Enter the full name of the organization on the confirmation page that appears, then click **Delete Account**. ### Uploading packages to an organization from the command line To upload a package to an organization, open Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux) and run the following command: ```sh theme={null} anaconda upload --user ``` Comments Replace \ with your organization name.\\ Replace \ with the name of the package. > [!NOTE] > > Only the co-owners of an organization might upload packages to the organization. # Tokens Source: https://anaconda.com/docs/anaconda-org/admin-guide/tokens Control who can access packages in a channel by associating the channel with a [group](/docs/anaconda-org/admin-guide/groups). This allows you to set separate permissions per package. You can further control access to your packages within organizations and groups with tokens (An access control token is a random alphanumeric string that is inserted into a package or channel URL. Tokens can be used with Anaconda.org, the Anaconda Premium Repository, or the AE4 Repository. The token allows you to download a package or add a channel that are restricted.). Tokens control access to private repositories, collections, or packages on Anaconda.org. Additionally, the degree of access a token grants is completely configurable at the time of generation. You can generate multiple tokens to control which groups of users have access to certain features if they have the appropriate token. > [!NOTE] > > Individual paid plans with private packages are a legacy offering from Anaconda.org that are no longer available. However, anyone who had private packages in the past still has the ability to have those hosted privately. [Private channels](/docs/anaconda-org/private-channels) offer a newer approach to private distribution using collaborator-based sharing instead of tokens. ## Generating tokens Tokens provide varying degrees of access to content within a specified channel (A location (URL or file path) in a repository where conda looks for packages.) depending on the scope assignment. If you need to separate permission levels by package, you can create an [organization](/docs/anaconda-org/admin-guide/organizations) and [groups](/docs/anaconda-org/admin-guide/groups) within that organization. > [!NOTE] > > By default, tokens expire after one year. **CLI** 1. Open Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux) and run the following command: ```sh theme={null} anaconda auth --create --name --scopes ' ' ``` Comments Replace \ with a name of your choosing.\\ Replace \ with a scope(s) from the Scopes dropdown below. This command generates a random alphanumeric string. That string is your token! You can distribute your token to other Anaconda.org users to provide them with a specific, limited set of permissions to interact with your Anaconda.org assets. 2. Add the token to your channel path in your .condarc file by running the following command: ```sh theme={null} conda config --add channels https://conda.anaconda.org/t// ``` Comments Replace \ with your token string.\\ Replace \ with the channel name. Or, add a channel with a token and a label (Part of the URLs on Anaconda.org where conda looks for packages. Labels are searched only if you specify a label.): ```sh theme={null} conda config --add channels https://conda.anaconda.org/t///label/ ``` Comments Replace \ with your token string.\\ Replace \ with the channel name.\\ Replace \ with the label name used in the previous step. > **Scopes** > > Assign scopes to tokens to set permission levels for token holders. Scopes are provided as a space-separated, quoted list. > > Available scopes: > > | Scope | Permission | > | :- | :- | > | `all` | Allow all operations | > | `repos` | Allow access to all package repositories | > | `pypi` | Allow all operations on Standard Python repositories | > | `pypi:upload` | Provides upload permissions to Standard Python repositories | > | `pypi:download` | Provides download permissions for private packages in Standard Python repositories | > | `conda` | Allow all operations on conda repositories | > | `conda:download` | Provides download permissions for private packages in conda repositories | > | `api` | Allow all API operations | > | `api:write` | Provides write permissions to actions performed via API | > | `api:read` | Provides read permissions to actions performed via API | > | `api:modify-group` | Provides manage permissions to groups via the API | **Anaconda.org** 1. Log in to Anaconda.org. 2. From your profile in the top-right corner, select **Settings**. 3. Select **Access** in the left-hand menu. 4. Fill out the Create access token form: 1. Provide a unique token name. 2. Set your token strength to `strong (longer token)`. This generates a strong, completely unique token that is difficult to guess with brute force methods. 3. Set the required scopes for your use case. 4. Set the expiration date. A notification appears containing your token. > [!TIP] > > You can view the token at any time at the bottom of the **Access** page. 5. Click **Create**. > [!NOTE] > > If your token expires, [revoke the token](#revoking-tokens) and create a new one. ## Revoking tokens You can revoke tokens directly on Anaconda.org or from the command line interface (CLI). **CLI** 1. Open Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux) and run the following command: ```sh theme={null} anaconda auth --remove ``` Comments Replace \ with the name of the token you want to revoke. **Anaconda.org** 1. Log in to Anaconda.org. 2. From your profile in the top-right corner, select **Settings**. 3. Select **Access** in the left-hand menu. 4. At the bottom of the page, click the name of the token you want to revoke. 5. Click **Revoke Token**. # Artifact detail pages Source: https://anaconda.com/docs/anaconda-org/artifact-details Every package, environment, and model on Anaconda.org has a detail page with in-depth information. You can reach a detail page by selecting a card from the [search results](/docs/anaconda-org/searching), clicking an artifact name anywhere it appears on the site, or navigating directly to its URL. **Packages** ![An overview of the package details page for the Python package on Anaconda.org](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-org/org_package_info.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=0e63bed0fe0d9ea27b991e41168a9040) **1. Package introduction** This section contains: * Breadcrumbs linking back to the package's channel (channel / package). Select the channel to [view its homepage](/docs/anaconda-org/channels). * The name of the package. * A badge describing whether the package is Anaconda Curated (This package has been verified by Anaconda for quality, security, and compatibility. Anaconda Terms of Service apply.) or Community (This package is maintained by the open-source community. Free to use under open-source licenses. Maintained by volunteer contributors and community organizations.) built. * A short package description. **2. Tabs** A set of tabs giving you access to more package information:
Overview
General information further outlined in the descriptions below. Selected by default.
Files
Lists of package [archive files](/docs/anaconda-org/maintainer-guide/package-files) (such as `.conda` and `.tar.bz2`) that you can download.
Labels
A list of package [labels](/docs/anaconda-org/maintainer-guide/labels) created by the package maintainer.
Badges
A list of badges relevant to the selected package and resources for embedding the badges in your web page.
> [!NOTE] > > Packages from the [conda-pypi](https://anaconda.org/channels/conda-pypi) channel display a simplified detail page with the **Overview** and **Files** tabs only. The **Labels** and **Badges** tabs are not available for conda-pypi packages.
**3. Version** Use the dropdown to select the package version you want to download. The information on the **Overview** tab changes when the version changes. The latest version is selected by default. **4. Installation** Installation commands for the package version selected. Select the command to copy it for use in your command line interface (CLI). **5. Install via Anaconda Desktop** Click **Install via Anaconda Desktop** to install this package into your environment using Anaconda Desktop. For more information, see [Packages](/docs/anaconda-desktop/packages). **6. Try This Package** > [!NOTE] > > This feature is in beta and is only available for certain packages. Run a pre-made code example using the package to see how it works. You can also use the "Your own example" option to create your own code using the package right in the browser. The Try This Package feature is powered by [PyScript](https://pyscript.net/). **7. Usage Tracking** Use the Downloads and Updates tables to view the usage statistics for your selected package.
Downloads table
Compares download numbers within the last six months. Use the **Version** dropdown above the table to add or remove package versions you want to compare.
Updates table
Displays number of updates released by the package's maintainers. Select *Monthly* to view updates within the last four months or *Weekly* to view updates within the last six weeks.
**8. Description** A description of the selected package. **9. Compare button** An **Compare** button for comparing this package to others. For more information, see [Comparing packages](/docs/anaconda-org/comparing-packages). **10. About** General information about the selected package, including the date and time when the package was last updated, the package's license, supported (and unsupported) platforms and architectures, and relevant links for more information about the package. **Environments (Beta)** ![An environment details page on Anaconda.org](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-org/org_environment_details.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=9df3ce787864d68c2c1b36fcc102c5e2) **1. Environment introduction** This section contains: * Breadcrumbs linking back to the environment's organization (organization / environment). Select the organization to [view its channel homepage](/docs/anaconda-org/channels). * The name of the environment. * A badge describing that the environment is Anaconda Curated (Maintained and tested by Anaconda. These environments receive priority support. Anaconda Terms of Service apply.). * A short environment description. **2. Installation** Commands to install the environment with conda. Click **Download environment.yml** to download the environment's `.yml` file to your computer. > [!TIP] > > The downloaded `environment.yml` file is saved to your Downloads folder. To use the install command as-is, either move the file to your current working directory or specify the full path to the file: > > **Windows** > > ```sh theme={null} > conda env create -f %USERPROFILE%\Downloads\environment.yml > ``` > > **macOS/Linux** > > ```sh theme={null} > conda env create -f ~/Downloads/environment.yml > ``` **3. Packages** The full list of packages included in the environment. Any pinned version specifications will also be listed with the corresponding package. **4. About** General information about the selected environment, including the date and time when the environment was last updated, whether or not the environment contains a lockfile, supported (and unsupported) platforms and architectures, channels the environment uses, and tags associated with the environment. **Models** ![A model detail page on Anaconda.org](https://mintcdn.com/anaconda-29683c67/AnulB1yCwg3TQDeL/images/anaconda-org/org_model_details.png?fit=max\&auto=format\&n=AnulB1yCwg3TQDeL\&q=85\&s=46f0fae199e041405eff27faf104394e) **1. Model introduction** This section contains: * The model name. * The publisher. * Sign-in required A dropdown menu to select the model variant or quantization you want to view. > **About quantizations** > > You can select which quantization to use for a model. Each quantization is a separate, pre-built version of a model stored as a GGUF (`.gguf`) file. Quantization reduces the precision of a model's weights, converting them from high-precision floating point values to lower bit depths like 8-bit or 4-bit integers. This shrinks file size and RAM requirements at the cost of some output quality. > > **Reading quantization names** > > Anaconda models use a naming convention that encodes the bit depth and quantization method. For example, `q4_k_m` means a 4-bit quantization using the medium-variant K-quant method. > > PartMeaningExample > > `q` + numberBits per weight. Lower numbers mean smaller files and lower RAM usage, but reduced accuracy.`q4` = 4 bits,\ > `q8` = 8 bits > > `_k`K-quant method. Allocates bits more intelligently across model layers to improve quality at a given size compared to the legacy method.`q4_k` > > `_s`, `_m`, `_l`Size variant within a K-quant level: small, medium, or large. Larger variants use slightly more memory but produce better output quality.`q4_k_m` > > `_0`Legacy quantization scheme. Generally less efficient than K-quant variants at the same bit depth.`q8_0` > > `f16`16-bit floating point with no quantization applied. Highest accuracy, but largest file size and RAM requirements.`f16` > > **Choosing a quantization** > > Select a quantization based on your hardware and accuracy needs: > > * **Lower bit depth (`q2`-`q4`)**: Smaller files, lower RAM usage, and faster inference, but noticeably reduced output quality. Best suited for resource-constrained hardware. > * **Mid-range (`q5`-`q6`)**: A practical balance between size and quality that works well on most hardware. > * **Higher bit depth (`q8`, `f16`)**: Near full-precision output quality, but requires significantly more RAM and disk space. > > Lower quantization levels are well-suited for development and testing due to their lower memory requirements. Higher quantization levels preserve more model fidelity and are better suited for production use. **2. Install via Anaconda Desktop** Click **Install via Anaconda Desktop** to open the model in [Anaconda Desktop](/docs/anaconda-desktop/model-catalog) for local download and use. If you do not have Desktop installed, you are prompted to download and install it. **3. Evaluation Scores** Sign-in required The evaluation scores for the model, including various benchmarks and performance metrics. **4. Legal** Sign-in required The license specifications for the model. **5. About** General information about the model, including a description, model type, size, RAM, tags, the date it was published, and various informational links. > **About model types and tags** > > A model's type reflects its training objective and architecture. Anaconda.org currently includes the following model types: > >
>
`Text Generation`
> >
These models produce coherent, contextually relevant natural language based on user input. Common use cases include content creation, coding assistance, and conversational AI.
> >
`Sentence Similarity`
> >
These models encode text into a vector database (embedding) that captures semantic meaning, enabling efficient comparison and analysis of text based on contextual relationships. Common use cases include semantic search and recommendation systems.
> >
`Image Text to Text`
> >
These models accept both text and image inputs and produce text output. They can be used for tasks such as image captioning, visual question answering, and document understanding. When running as an API server, these models can process image inputs sent directly to the server.
>
> > Tags reflect what a model can do beyond its primary purpose. For example, a `Text Generation` model might also support code generation. Notable tags include: > > * `Embedding`: The model can generate vector representations of text for use in semantic search, RAG pipelines, and similarity comparisons. > * `Tool Calling`: The model can invoke external tools or APIs to retrieve information or perform actions during inference. > * `Code Generation`: The model can produce, complete, or transform source code across one or more programming languages. > * `Guardrail`: The model is designed to evaluate or filter content, typically used to enforce safety or policy constraints in AI pipelines. > * `Base Model`: The model has not been fine-tuned for a specific task and is intended as a foundation for further training or customization. > * `Instruction Following`: The model has been trained to respond reliably to structured instructions or prompts. # Viewing channel information Source: https://anaconda.com/docs/anaconda-org/channels There are several ways to view a channel's homepage: * Select the channel from a package's details page. * Use the **List view** for your search results, then select a channel from the **Channel** column. * Navigate to `anaconda.org/channels/`, where `` is the name of the channel. This can be an organization or user channel. The channel's homepage displays the most popular packages in the channel, a set of download statistics for the channel (by month or week), channel usage instructions, and a searchable list of all packages available in the channel. ![A screenshot of the channel homepage for the Anaconda main channel on Anaconda.org](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-org/org_channel_homepage.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=d0cee76e2f04440d68885ba998bdc07b) Notable channels you can browse on Anaconda.org include: * [main](https://anaconda.org/channels/main) — Anaconda's default channel, containing thousands of curated packages for data science and AI. * [conda-forge](https://anaconda.org/channels/conda-forge) — A community-maintained collection of conda packages. * [conda-pypi](https://anaconda.org/channels/conda-pypi) — A channel that indexes pure Python wheels from PyPI, allowing you to install them with conda. Requires conda 26.9.x or later and the rattler solver. For setup instructions, see the [official conda documentation](https://docs.conda.io/projects/conda/en/stable/user-guide/tasks/install-packages-from-pypi.html). # Comparing packages Source: https://anaconda.com/docs/anaconda-org/comparing-packages Anaconda.org's package comparison tool lets you evaluate up to five packages side by side, making it easier to choose the right one for your project. ## Adding packages to a comparison Enter Compare mode by clicking **Compare** in the search results page or on a package's details page. Once you are in Compare mode, you can add up to five packages to the comparison. * If you entered Compare mode from a package details page, that package will be added to the comparison automatically. * If you entered Compare mode from the search results page, you can add more packages by clicking **Compare** on each package card. You can continue to navigate Anaconda.org normally without exiting Compare mode. Search for new packages and select their checkboxes to add them to the comparison, or navigate to a package's details page and click **Add to comparison**. Any packages added to the comparison are visible at the bottom of the page in the comparison queue. Click the close x beside a package to remove it from the comparison. ![An example of adding the conda-forge python package to Compare mode in Anaconda.org](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-org/org_package_add_to_comparison.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=b63af1788e6468eef555d8e92dc8233e) ## Comparing packages Once you are satisfied with your package comparison selections, click **Compare** to see the comparison results. ![A comparison between two different python packages](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-org/org_package_comparison.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=f8136b85ac30ae43953b434f7b09cc8a) The Compare Packages page compares up to five packages by criteria such as channel source, date last updated, total downloads, license, and compatible platforms. Click the package name to open the package details page for that package. Click and drag the move handle to reorder your comparisons. Select other versions of any of the packages you are comparing using their **Version** dropdowns. Click **Add Package** to exit the Compare Packages page and search for other packages to add to the comparison queue. Click **Share Comparison** to copy a link to your comparison to share with others. Sharing comparisons and viewing shared comparisons both require sign-in. Click **Clear All** to clear your comparison selections and exit Compare mode. # FAQs Source: https://anaconda.com/docs/anaconda-org/faq ## What is Anaconda.org? [Anaconda.org](https://anaconda.org/) is a package (Software files and information about the software, such as its name, the specific version, and a description, that are bundled into a file that can be installed and managed by a package manager.) management service by [Anaconda](https://www.anaconda.com/). For more information on Anaconda.org's features, see [Key features](/docs/anaconda-org/key-features). ## What kind of packages does Anaconda.org support? Anaconda.org is primarily used for conda and standard Python packages. Both `tar.bz2` and `.conda` compression files can be uploaded to Anaconda.org. ## Who can find and install my packages? All of your packages are public. After you upload them to Anaconda.org, anyone can [search for](/docs/anaconda-org/searching) and [install](/docs/anaconda-org/installing-packages) them. ## What are Anaconda.org's Terms of Service? Anaconda's [Terms of Service](https://anaconda.com/legal) are available on our website. For any additional questions, contact us by [email](mailto:sales@anaconda.com). ## How much does Anaconda.org cost? Anaconda.org is free for downloading and uploading public packages. ## How do I get started with Anaconda.org? You can search for, download, and install hundreds of public packages without having an account. To upload packages, sign up for an [Anaconda account](/docs/anaconda-org/accounts). For more information on getting started with Anaconda.org, see [Getting started](/docs/anaconda-org/maintainer-guide/getting-started). ## What kind of account do I have? Your account is a personal, free account by default. All packages you upload to Anaconda.org are public, and you are the only person with administrative access to your account. Your account is also provided with up to 3GB of storage space for any packages you upload. ## What is an organization account, and how is it different from an individual account? An organization account allows multiple individual users to administer packages and have more control of package access by other users. An individual account is for use by one person. For more information on organizations, see [Organizations](/docs/anaconda-org/admin-guide/organizations). # Getting started with Anaconda.org Source: https://anaconda.com/docs/anaconda-org/getting-started > [!NOTE] > > Anaconda is releasing a new user experience that is affecting some of the pages on Anaconda.org. Search and the package details pages have a new look and feel, but be aware that some pages will still have the old interface for now. Anaconda.org is a public platform for sharing open-source software packages. If you're just curious about what's available, you can browse available packages without creating an account. With an account, you can upload your packages you've built to share with others. You can also create an organization to manage shared channels and control who has access to your uploaded packages. * To learn the fundamentals of Anaconda.org, see [Basics](#basics). * To learn how to upload and manage packages in your account, see [Options for package maintainers](#options-for-package-maintainers). * To learn how to set up your team and control access to your packages, see [Creating and managing an organization](#creating-and-managing-an-organization). ## Basics > **[Search Anaconda.org](/docs/anaconda-org/searching)** > > Find packages, environments, and AI models using search and filters > **[Compare packages](/docs/anaconda-org/comparing-packages)** > > Evaluate packages side by side to choose the right one > **[Installing packages](/docs/anaconda-org/installing-packages)** > > Install packages onto your computer with Anaconda Navigator or conda > **[Creating an account](/docs/anaconda-org/accounts)** > > Create a user account to do even more with Anaconda.org ## Creating and managing an organization > **[Organizations](/docs/anaconda-org/admin-guide/organizations)** > > Create and manage an organization > Private channels > Beta > > Distribute packages privately to specific collaborators > > [Open](/docs/anaconda-org/private-channels) > **[Groups](/docs/anaconda-org/admin-guide/groups)** > > Organize your users and teams with groups > **[Tokens](/docs/anaconda-org/admin-guide/tokens)** > > Control access permissions for packages and channels ## Options for package maintainers > **[Get started](/docs/anaconda-org/maintainer-guide/getting-started)** > > Use your Anaconda account to start your package maintainer journey > **[Upload packages](/docs/anaconda-org/maintainer-guide/upload-packages)** > > Upload your own conda and standard Python packages for public use > **[Maintain packages](/docs/anaconda-org/maintainer-guide/hosted-packages)** > > Edit your package landing pages, descriptions, labels, and more # Installing packages Source: https://anaconda.com/docs/anaconda-org/installing-packages You can install packages from Anaconda.org channels using Anaconda Desktop, Anaconda Navigator, or by using conda in a command line interface (CLI) with Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux). > [!NOTE] > > If you don't have Anaconda Desktop, you can [download it](https://www.anaconda.com/products/desktop) from Anaconda.com. > > For more information on installing Anaconda Desktop, see [Installing Desktop](/docs/anaconda-desktop/install-desktop). > > *** > > [Navigator](/docs/legacy/anaconda-navigator/main) is automatically installed when you [install Anaconda Distribution](/docs/getting-started/installation). > > Miniconda users can obtain Navigator by running `conda install anaconda-navigator`. **Anaconda Desktop** > [!TIP] > > To install a package directly from Anaconda.org, click **Install via Anaconda Desktop** from the package's details page. 1. Open Anaconda Desktop. 2. Select **Environments** from the left-hand navigation. 3. Select one of your environments or click **Create** to create a new one. 4. Click **Package**. 5. Search for your package by name using the **Search** box. 6. Select the checkbox beside the package you want to install, then click **Add Package**. 7. Review the package updates for your environment. Desktop displays all package modifications necessary to add your selected package. 8. Click **Apply Changes** to update your environment. For more information on installing packages with Anaconda Desktop, see [Packages](/docs/anaconda-desktop/packages). **Navigator** Navigator is automatically installed when you install Anaconda. Miniconda users can obtain Navigator by running `conda install anaconda-navigator`. To install a package into a local environment: 1. Open Anaconda Navigator. 2. Select **Connect**, then select **SIGN IN** beside Anaconda.org. 3. Enter your username and password and select **Sign In** to connect Navigator to Anaconda.org. 4. Select **Environments** from the left-hand navigation. 5. Select one of your environments or select **Create** to create a new one. 6. Select *Not installed* from the dropdown beside the **Channels** button. 7. Look for your package by name using the **Search Packages** field. 8. Select the checkbox of the package you want to install, then select **Apply**. 9. Navigator will then display the list of packages necessary to install your selected package. Select **Apply** to install all packages to your environment. For more information on using Navigator, see Navigator's [Getting started](/docs/legacy/anaconda-navigator/getting-started) page. **CLI** To install a package into a local environment: 1. Create a new environment or activate an existing environment. ```sh Create a new environment theme={null} conda create -n ``` ```sh Activate an existing environment theme={null} conda activate ``` Comments Replace \ with the name of your environment. 2. [Locate a package on Anaconda.org](/docs/anaconda-org/searching) that you want to install, then select the package's card. 3. The package's details page displays specific installation instructions. Copy and paste the full command into your terminal window. This command will look different, depending on what kind of package you are installing: ```sh Conda package theme={null} conda install :: ``` ```sh conda-pypi package theme={null} conda install conda-pypi:: --solver rattler ``` ```sh Standard Python package theme={null} pip install -i https://pypi.anaconda.org//simple ``` Comments Replace \ with the channel containing the package. This could be a username or an organization.\\ Replace \ with the name of the package you want to install. > [!NOTE] > > The conda-pypi channel requires conda 26.9.x or later and the rattler solver. You can set the rattler solver as your default with `conda config --set solver rattler`, or specify it per command with the `--solver rattler` flag. For full setup instructions, see [Installing packages from PyPI with conda](https://docs.conda.io/projects/conda/en/stable/user-guide/tasks/install-packages-from-pypi.html) in the official conda documentation. For more information on the package details page, see [Searching Anaconda.org](/docs/anaconda-org/searching). # Anaconda.org Source: https://anaconda.com/docs/anaconda-org/key-features > [!NOTE] > > Anaconda is releasing a brand new user experience for Anaconda.org. These changes are ongoing, so be aware that some pages will still have the old user interface. Anaconda.org is a cloud-based package (Software files and information about the software, such as its name, the specific version, and a description, that are bundled into a file that can be installed and managed by a package manager.) repository and distribution platform primarily for conda and Python packages. Anaconda provides this package hosting and management service to the open source community, so that you or your organization can improve your development workflows with thousands of open-source packages. [Custom accounts](https://www.anaconda.com/pricing) should use Anaconda.com for package access. ## Key features ### Package repository search * **Comprehensive package library**: Anaconda.org hosts thousands of pre-built, open-source packages commonly used in data science, scientific computing, and machine learning. The platform supports packages for Python and many other programming languages, including Julia, Scala, and C++. * **Advanced search filtering**: Search for packages by name (or partial name) and filter your results by channel, license, and platform (system architecture). Available channels include Anaconda's `main` channel, conda-forge, the conda-pypi channel for pure Python wheels, and thousands of user and organization-created channels. * **Try This Package** Beta: Run pre-made (or custom) code examples using a package directly in the browser to see how it works. Powered by [PyScript](https://pyscript.net/). * **Compare packages**: Compare up to five packages side by side by criteria such as channel source, date last updated, total downloads, license, and compatible platforms. ### Environment browse * **Discover pre-built environments** Beta: Browse and search quickstart conda environments built by Anaconda. Find environments for common use cases like machine learning, NLP, bioinformatics, and computer vision. * **Install with a single command** Beta: Once you find an environment that fits your needs, install it on your local machine with one command. ### Upload and publish packages * **Anaconda Client tool**: The `anaconda-client` package comes bundled with Anaconda Distribution or can be installed separately. This tool allows you to upload packages to your account or organization on Anaconda.org, streamlining package sharing with colleagues and teams or storing your personal work securely in the cloud. * **Channel and package management tools**: Upload packages to your account and create custom channels. Edit package and channel descriptions and control what packages your channels contain. * **Package labels**: Label your packages (such as `dev`, `test`, or `rc`) to better organize your development cycles and keep test packages away from production code. ### Private channels * **Distribute packages privately** Beta: Create [private channels](/docs/anaconda-org/private-channels) under an organization to share conda or wheel packages with specific collaborators instead of making them publicly available. * **Collaborator-based access** Beta: Share channels with individual users and assign viewer or collaborator roles to control who can install or upload packages. ### Organization management * **Team groups**: Administrative users can create groups within an organization, allowing for more precise package permissions per group. * **Access tokens**: Control package or channel access for individual users or groups with tokens (An access control token is a random alphanumeric string that is inserted into a package or channel URL. Tokens can be used with Anaconda.org, the Anaconda Premium Repository, or the AE4 Repository. The token allows you to download a package or add a channel that are restricted.). # Anaconda Client command reference Source: https://anaconda.com/docs/anaconda-org/maintainer-guide/command-reference # Getting started as a package maintainer on Anaconda.org Source: https://anaconda.com/docs/anaconda-org/maintainer-guide/getting-started Anaconda.org hosts Anaconda's main channel, but also thousands of packages uploaded by other users. To upload your own packages to Anaconda.org, follow this getting started guide. ### 1. Create an Anaconda account If necessary, sign up for an [Anaconda account](/docs/anaconda-org/accounts). ### 2. Install the anaconda-client package The Anaconda Client CLI tool lets you interact with Anaconda.org directly from your terminal. Upload packages you've built, download packages you need, manage your account settings, and control access to private repositories—all through command-line operations that integrate smoothly into your development workflow. If you installed Anaconda Distribution, you might already have it in your `base` environment. To find out if you have `anaconda-client` installed, open Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux) and run the following commands: ```sh theme={null} conda activate base conda list anaconda-client ``` If `anaconda-client` is installed properly, you'll see something like the following: ``` # packages in environment at /Users/annieconda/anaconda3: # # Name Version Build Channel anaconda-client 1.13.0 py311hca03da5_0 ``` > **I don't have anaconda-client installed** > > If your `base` environment is missing `anaconda-client`, you can install it with [conda](https://docs.conda.io/en/latest/), [pip](https://pip.pypa.io/en/latest/), or pip from source. Anaconda recommends using conda. > > ```sh conda theme={null} > conda install anaconda-client anaconda-auth > ``` > > ```sh pip theme={null} > pip install anaconda-client anaconda-auth > ``` > > ```sh pip from source theme={null} > pip install git+https://github.com/anaconda/anaconda-client git+https://github.com/anaconda/anaconda-auth > ``` ### 3. Log into Anaconda.org from the command line Run the following command to log into your Anaconda account: ```sh theme={null} anaconda org login ``` Log in with your Anaconda credentials. Once you have logged in and installed `anaconda-client`, you can begin uploading packages to your account on the command line. Find your account's channel by navigating to `anaconda.org/channels/`, where `` is your Anaconda.org username. For more information about channel homepages, see [Viewing channel information](/docs/anaconda-org/channels). ## Next steps * [Search for packages](/docs/anaconda-org/searching) or [explore channels](/docs/anaconda-org/channels) * Review Anaconda Client commands, options, and arguments in the [Anaconda Client command reference](/docs/cli-reference/anaconda-client/getting-started). * [Build your own conda packages](/docs/anaconda-org/maintainer-guide/upload-packages) and upload them to Anaconda.org. ## Getting help To display a list of Anaconda Client commands, open Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux) and run the following command: ```sh theme={null} anaconda --help ``` To find out more about an Anaconda Client command, run: ```sh theme={null} anaconda -h ``` Comments Replace \ with the name of the command you want more information about. You can also visit the [Anaconda community forums](https://forum.anaconda.com/) to request help with specific issues. # Managing your hosted packages Source: https://anaconda.com/docs/anaconda-org/maintainer-guide/hosted-packages Anaconda.org has many options for managing the information associated with your hosted packages or for managing package permissions and access to collaborators or members of your organization. ## Adding a collaborator to a package You can add other users that are not part of an organization to collaborate on your packages. 1. From your dashboard, select the package. 2. Select **Manage**. 3. To display the package settings, select the **Settings** option. 4. To display the current collaborators, select the **Collaborators** option. 5. Enter the username of the person you want to add as a collaborator, then click **Add**. > [!NOTE] > > All collaborators are given full read/write permissions to the package, *even for private packages*. ## Removing a collaborator from a package To revoke package access previously granted to a collaborator: 1. From your dashboard, select the package. 2. Select **Manage**. 3. To display the package settings, select the **Settings** option. 4. To display the current collaborators, select the **Collaborators** option. 5. Click the red **X** beside a collaborator to revoke their access. ## Transferring a package to a new owner By default, when you create or add packages, they are attached to your individual profile. You can transfer ownership to another owner account you control, such as an organization profile you manage. To transfer a package to a new owner: 1. From your dashboard—or the dashboard of an organization you administer—select the package for which you want to transfer ownership. 2. Select **Manage**. 3. To display the package settings, select the **Settings** option. 4. Select the **Admin** option. 5. Under **Transfer this package to a new owner**, click **Transfer**. 6. Select the organization name for the new owner. 7. Click **Transfer Ownership**. ## Copying a package The following command is an example of how to copy a package from the `conda-forge` channel to a personal channel called `jsmith`: ```sh theme={null} anaconda copy conda-forge/glueviz/0.10.4 --to-owner jsmith ``` `conda-forge/glueviz/0.10.4` is a "spec" that can be formatted in one of two ways: `user/package/version` or `user/package/version/filename`. > [!WARNING] > > The `anaconda copy` commands `from-channel` and `to-channel` have been deprecated. If you attempt to run `anaconda copy --from-channel conda-forge --to-channel jsmith glueviz`, you will receive an error that `Label conda-forge does not exist`. > [!WARNING] > > If the package `glueviz/0.10.4` already exists for user `jsmith`, you will receive the following error message: `File conflict while copying!`. If you want to copy the package anyway, try prepending the command with one of the following flags: > `--replace` - allows you to overwrite an already existing package > > `--update` - allows you to add missing metadata to an existing package ## Removing a previous version of a package To remove a previous version of one of your packages from Anaconda.org: 1. From your dashboard, select the package. 2. Select **Manage**. 3. Navigate to the **Files** tab. 4. Select the checkbox to the left of the version you want to remove. 5. In the **Actions** menu, select **Remove**. To remove a previous version of one of your packages using Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux), run: ```sh theme={null} anaconda remove // ``` Comments Replace \ with your username.\\ Replace \ with the package name.\\ Replace \ with the preferred version. You can now see the change on your profile page at `http://anaconda.org//`, where `` is your username and `` is the package name. ## Hiding package install instructions After you have uploaded packages to an account or organization, you can control what install instructions appear on your package's download page. Install instructions will vary depending on the package's labels or package type (conda or standard Python). To edit the visibility of your package install instructions: 1. From your dashboard, select the package. 2. Select **Manage**. 3. Select **Edit**. 4. Select the checkboxes for the instructions you want to hide. You can also select the checkbox on the far right of any group to hide all instructions. 5. Select **Save Changes**. ![A set of selection options for making install instructions visible on the package detail page](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-org/org-package-install-hide.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=079c652ddfb47335c6b061976989cbe0) ## Deleting a package You can delete packages using Anaconda.org's user interface or by using a command line interface (CLI), such as Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) on Windows or Terminal on macOS/Linux. **Using Anaconda.org** To delete a package and all of its versions from Anaconda.org: 1. From your dashboard, select the package. 2. Select **Manage**. 3. Select the **Settings** option. 4. Select the **Admin** option. 5. Click **Delete**. **Using the CLI** To delete a package and all of its versions using Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux), run: ```sh theme={null} anaconda remove / ``` Comments Replace \ with your username.\\ Replace \ with the package name. The removed package will no longer appear in the list of packages on your profile page at `http://anaconda.org/`, where `` is your Anaconda.org username. ## Updating package metadata Much of the metadata provided in your package's meta.yaml file appears on your package's download page. This is information like your package's license, description, Git repository URL, and documentation URLs. For more information on what is usually contained in conda-build's meta.yaml file, see the [conda-build documentation](https://docs.conda.io/projects/conda-build/en/latest/resources/define-metadata.html). Anaconda Client automatically updates metadata defined in the meta.yaml file of your package upload, *as long as the package version number has never been uploaded previously*. To update your metadata without needing a new package version, use `--force-metadata-update`. ```sh theme={null} anaconda upload /your/path/conda-package.tar.bz2 --force-metadata-update ``` # Labels Source: https://anaconda.com/docs/anaconda-org/maintainer-guide/labels Labels (Part of the URLs on Anaconda.org where conda looks for packages.) on Anaconda.org help you organize packages and control their visibility. By applying labels to packages, you can facilitate the development cycle—separating development, testing, and production code—without impacting users who only want stable releases. Using Anaconda Client, package developers can create labels like `dev` for development, `test` for testing, or `rc` for release candidates. ## Understanding labels By default, conda only finds packages labeled `main`. If you don't specify a label when uploading, your package automatically gets the `main` label. However, you can use other labels such as `dev`, `test`, or `any-custom-label` to effectively "hide" a package or package version from conda's default search and install behavior. Users can still access the labeled package on Anaconda.org but must explicitly specify the label to find and install the package with conda. > [!WARNING] > > Anaconda.org web URLs use `/labels` (plural) while conda commands use `/label` (singular). The following examples use a Namespace (Each user and organization has their own location called a 'namespace' where they can host packages. You can view the public packages in a user or organization's namespace by navigating to their user page.) of `travis`: | Web Interface | Conda Command | What it contains | | :- | :- | :- | | `anaconda.org/travis` | `conda install --channel travis ` | Default packages (`main` label only) | | `anaconda.org/travis/labels/main` | `conda install --channel travis/label/main ` | Explicitly accessing `main` label | | `anaconda.org/travis/labels/dev` | `conda install --channel travis/label/dev ` | Development packages | | `anaconda.org/travis/labels/test` | `conda install --channel travis/label/test ` | Testing packages | ## Using labels to control package visibility The following steps explain how to apply a `test` label, which allows you to upload files without affecting your production-quality packages, then how to apply the `main` label to make it visible to conda. ### Building and uploading the package Use Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux) to perform the following steps: 1. Start with a conda package (An archive file containing a software program and all its dependencies for easy installation. Conda automatically handles dependency tracking across different platforms, eliminating the need to manually install each component separately.). In this example, we use a small public [conda test package](https://github.com/Anaconda-Platform/anaconda-client/tree/master/example-packages/conda): ```sh theme={null} git clone https://github.com/Anaconda-Platform/anaconda-client/ cd anaconda-client/example-packages/conda/ ``` 2. Open the `meta.yaml` file by running the following command: ```sh theme={null} nano meta.yaml ``` 3. Change the version number to `2.0`. To save and close the `meta.yaml` file, press Ctrl+X, followed by Y. 4. To build the package, turn off automatic Client uploading and then run the `conda build` command: ```sh theme={null} conda config --set anaconda_upload no conda build . ``` > [!TIP] > > You can check where the resulting file was placed by adding the `--output` option: > > ```sh theme={null} > conda build . --output > ``` 5. Upload your test package to Anaconda.org using the Anaconda Client upload command. Add the `--label` option followed by your label (in this case, `test`), which tells Anaconda.org to make the upload visible only to users who specify that label: ```sh theme={null} anaconda upload .tar.bz2 --label test ``` Comments Replace \ with the correct file path and package name. Now you can see that even when you search conda `main`, you do not see the `2.0` version of the test package. This is because you need to tell conda to look for your new `test` label. ### Testing the discoverability of the package 1. Add the `--override` argument, which tells conda not to use any channels (A location (URL or file path) in a repository where conda looks for packages.) in your `~/.condarc` file. Without specifying the label and package name, the `2.0` version is not discoverable: ```sh theme={null} conda search --override --channel conda-package ``` Comments Replace \ with your username. Once the label and package are specified, the `2.0` can be found: ```sh theme={null} conda search --override --channel /label/test conda-package ``` Comments Replace \ with your username. 2. You can give the label `/label/test` to your testers, where `` is your username. 3. Once they finish testing, you might then want to copy the `test` packages back to your `main` label: ```sh theme={null} anaconda label --copy test main ``` You can also manage your package labels from your dashboard at `https://anaconda.org/USERNAME/conda-package`, where `` is your username. Your version `2.0` is now in `main`: ```sh theme={null} conda search --override --channel conda-package ``` Comments Replace \ with your username. If you use `anaconda-client` 1.7 or higher, you can use `anaconda move` to move packages from one label to another: ```sh anaconda move theme={null} anaconda move --from-label --to-label ``` ```sh Examples theme={null} # Move an entire set of files to a new label anaconda move --from-label main --to-label dev myusername/numpy/1.21.0 # Move a single file to a new label anaconda move --from-label main --to-label dev myusername/numpy/1.21.0/numpy-1.21.0-py39_0.conda ``` Comments Replace \ with the old label.\\ Replace \ with the new label. \\ Replace \ with the package file path to move. # Downloading package files Source: https://anaconda.com/docs/anaconda-org/maintainer-guide/package-files The **Files** tab on a package's details page lists the available archive files for that package. From this page, you can search and filter the file list to find a specific file, then download it directly. ## Downloading package files To download a package file, click **Download** in the **Actions** column. This downloads the archive file (`.tar.bz2`, `.conda`, `.whl`) for the package. > [!WARNING] > > Downloading a package file does not install it into an environment. For information on how to install packages using Anaconda Navigator or conda, see [Installing packages](/docs/anaconda-org/installing-packages). ## Locating a package file You can search for a specific package file by entering information such as its name, architecture, build, or version number in the **Search files** box. Click the info icon beside a file name to view detailed metadata for the selected package file. ![An overview of the package file list and filters for the Python package in Anaconda.org](https://mintcdn.com/anaconda-29683c67/XTSpR8a-Sn-FW1SQ/images/anaconda-org/org_package_files.png?fit=max\&auto=format\&n=XTSpR8a-Sn-FW1SQ\&q=85\&s=17e88251ef758497eed3e72de0351dde) Click the filter icon to filter the package lists by the following criteria:
Versions
The available versions for the package.
Architecture
The available operating system architectures for the package.
Size (MB)
The size of the package archive file. Adjust the **Min size** and **Max size** values to narrow your selection.
Upload Date
The date when the package file was last updated. Enter dates manually or use the calendar tool to create a date range.
Labels
The [labels](/docs/anaconda-org/maintainer-guide/labels) associated with the packages.
Click **Clear** to clear any filter changes. # Private packages Source: https://anaconda.com/docs/anaconda-org/maintainer-guide/private-packages > [!NOTE] > > Individual paid plans with private packages are a legacy offering from Anaconda.org that are no longer available. However, anyone who had private packages in the past still has the ability to have those hosted privately. > [!TIP] > > Looking to distribute packages privately? [Private channels](/docs/anaconda-org/private-channels) let you create channels with collaborator-based access control. Logged in users can install packages you share using these private channels. ## Making packages private By default, all packages uploaded to Anaconda.org are accessible to anyone who has access to the repository (Any storage location from which software or software assets, like packages, can be retrieved and installed on a local computer.). To mark packages uploaded to your user channel (A location (URL or file path) in a repository where conda looks for packages.) on Anaconda.org as private: 1. From your dashboard, select the package. 2. Select **Manage**. 3. Navigate to the **Settings** tab. 4. Select **Admin** in the sidebar. 5. Select **Private**. > [!NOTE] > > Other Anaconda.org users might access your private packages either with tokens or by logging in. ## Accessing private packages with tokens To make your private packages accessible with tokens (A randomly generated string that proves your identity and permission to access resources like channels, packages, or APIs.), create an [access token](/docs/anaconda-org/admin-guide/tokens) that includes the following scope for Anaconda Client: ```sh theme={null} conda:download ``` Or, on Anaconda.org in the access settings, select **Allow private downloads from conda repositories**. ### Using the token to access private packages If you intend to install many packages from a private channel, you can include the channel in your `.condarc` file. This will include the token any time you search for packages on that channel. To add a user channel to your `.condarc` file from Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux), run the following command: ```sh theme={null} conda config --add channels https://conda.anaconda.org/t// ``` Comments Replace \ with the provided token.\\ Replace \ with a user channel. You can also use the token to install packages without first adding the channel to your `.condarc` file by using the channel's full URL. In Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux), run the following command: ```sh theme={null} conda install --channel https://conda.anaconda.org/t// ``` Comments Replace \ with the provided token.\\ Replace \ with a user channel.\\ Replace \ with the name of the package you want to install. ### Accessing a private package that has a label To install a package from a channel using the token and label (Part of the URLs on Anaconda.org where conda looks for packages. Labels are searched only if you specify a label.) name: ```sh theme={null} conda install --channel https://conda.anaconda.org/t///label/ ``` Comments Replace \ with the provided token.\\ Replace \ with a user channel.\\ Replace \ with the label name.\\ Replace \ with the name of the package you want to install. ### Using the token to access private PyPI packages Private PyPI packages can also be installed in the web UI: ```sh theme={null} https://pypi.anaconda.org/t// ``` Comments Replace \ with the provided token.\\ Replace \ with a user channel. ## Accessing private packages as a registered user To make your private packages available to users who have logged in: 1. Create an [organization](/docs/anaconda-org/admin-guide/organizations). 2. Create a group (which can be read-only) in that organization. 3. Add the preferred users to the group. 4. Upload the package to the organization, or transfer an existing package to the organization. After you grant users access, other users can install your package using the web UI or Anaconda Client. To install a package: 1. In a browser, navigate to the preferred channel. 2. Open Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux) and run the following command: ```sh theme={null} conda install anaconda-client anaconda login conda install --channel https://conda.anaconda.org/ ``` Comments Replace \ with the organization name.\\ Replace \ with the package name. ### Private channels You can install a package from a private channel with a token (A randomly generated string that proves your identity and permission to access resources like channels, packages, or APIs.) and a [Label](/docs/anaconda-org/maintainer-guide/labels): ```sh theme={null} conda install --channel https://conda.anaconda.org/t///label/ ``` Comments Replace \ with the provided token.\\ Replace \ with a user channel.\\ Replace \ with the label name.\\ Replace \ with the name of the package you want to install. Tokens are only required if the channel is private. ## Finding help for uploading packages You can obtain a complete list of upload options, including: * Package channel * Label * Availability to other users * Metadata To list the options, run the following in Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux): ```sh theme={null} anaconda upload -h ``` # Uploading packages Source: https://anaconda.com/docs/anaconda-org/maintainer-guide/upload-packages ## Uploading conda packages This example shows how to build and upload a [conda](https://docs.conda.io/projects/conda-build/en/stable/index.html) package to Anaconda.org using `conda build`. 1. Open Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux). 2. If necessary, install the `anaconda-client` and `conda-build` packages by running the following command: ```sh theme={null} conda install anaconda-client conda-build ``` 3. Choose the repository for which you would like to build the package. In this example, we use a small public [conda test package](https://github.com/Anaconda-Platform/anaconda-client/tree/master/example-packages/conda): ```sh theme={null} # Replace with the package name git clone https://github.com/Anaconda-Platform/anaconda-client cd anaconda-client//conda/ ``` There are two required files in the example package: [meta.yaml](https://github.com/Anaconda-Platform/anaconda-client/blob/master/example-packages/conda/meta.yaml) and [build.sh](https://github.com/Anaconda-Platform/anaconda-client/blob/master/example-packages/conda/build.sh). macOS and Linux systems are Unix-like systems. Packages built for Unix-like systems require a `build.sh` file, packages built for Windows require a `bld.bat` file, and packages built for both Windows and Unix-like systems require both a `build.sh` file and a `bld.bat` file. All packages require a `meta.yaml` file. 4. To build the package, turn off automatic client uploading and then run the `conda build` command: ```sh theme={null} conda config --set anaconda_upload no conda build . ``` All packages built using the `conda build` command are placed in a subdirectory of the [Anaconda](/docs/getting-started/concepts/anaconda-or-miniconda) `conda-bld` directory. > [!TIP] > > You can check where the resulting file was placed by adding the `--output` option: > > ```sh theme={null} > conda build . --output > ``` 5. Upload the test package to Anaconda.org by running the `anaconda upload` command: ```sh theme={null} anaconda login anaconda upload .tar.bz2 anaconda upload .conda ``` Comments Replace \ with the correct file path and package name.\\ Packages can be uploaded with `.tar.bz`2 or `.conda` compression formats. For more information on the `.conda` format, see [Using the .conda compression format](https://docs.conda.io/projects/conda/en/latest/user-guide/concepts/packages.html#conda-file-format). For more information on conda's overall build framework, see [Building conda packages](https://docs.conda.io/projects/conda-build/en/stable/concepts/recipe.html) in the official conda docs. ## Uploading standard Python packages You can test standard Python package uploading with a small public example package saved in the [anaconda-client repository](https://github.com/Anaconda-Platform/anaconda-client/tree/master/example-packages/pypi). Use Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux) to perform the following steps: 1. Clone the repository: ```sh theme={null} # Replace with the package name git clone git@github.com:Anaconda-Platform/anaconda-client.git cd anaconda-client//pypi/ ``` 2. Create your standard Python package using the `setup.py` script: ```sh theme={null} python setup.py sdist ``` 3. Upload your newly built package tarball file: ```sh theme={null} anaconda upload dist/*.tar.gz ``` Your package is now available at `http://anaconda.org//`, where `` is your username and `` is the package name. ## Uploading packages with GitHub Actions To automate package uploads as part of a CI/CD pipeline, or to migrate existing CLI-based upload workflows, see [Anaconda GitHub Actions](/docs/cli-reference/anaconda-cli/github-actions#upload-package). ## Additional help for uploading packages To view a complete list of upload options, including channel, label, availability, and metadata options, run the following in Anaconda Prompt (A command-line application included with Windows installations of Anaconda Distribution and Miniconda. Find it by searching 'Anaconda Prompt' in the Windows Start menu.) (Terminal on macOS/Linux): ```sh theme={null} anaconda upload -h ``` > **[Conda Essentials course](https://learning.anaconda.com/courses/conda-essentials)** > > Sign in to anaconda.com and enroll in this free course to learn to write conda recipes and build packages with `conda-build`. # Private channels Source: https://anaconda.com/docs/anaconda-org/private-channels Private channels let you distribute conda or wheel packages to specific people without making them publicly available. You create a private channel under an [organization](/docs/anaconda-org/admin-guide/organizations), upload packages to it, and then share access with collaborators using the CLI. Only users you explicitly share the channel with can see or install its packages. > [!NOTE] > > Private channels are distinct from [private packages](/docs/anaconda-org/maintainer-guide/private-packages), a legacy feature of Anaconda.org that restricts access to individual packages using tokens. Instead, private channels restrict access to an entire channel using a collaborator-based sharing model. > **Known limitations** > > The following limitations apply during the beta: > > * Channel namespaces must start with a lowercase letter and use only lowercase letters, numbers, underscores, and hyphens (up to 63 characters). To distribute packages from an account whose username does not match these rules, create the channel under an [organization](/docs/anaconda-org/admin-guide/organizations) instead. > * The number of private channels allowed per organization depends on your subscription plan: one for Free, three for Starter, and ten for Business. > * Only organization admins can create private channels. > * Creating a private channel in a personal namespace is available through the CLI only. On Anaconda.org, you can create private channels under an organization only. > * Uploading packages to and deleting packages from a channel are available through the CLI only. The Anaconda.org interface is read-only for channels. > * The declared package type must match the uploaded file's format. If the `--package-type ` value does not match the file's actual format, the upload fails with a generic `RepoCoreError: Something went wrong` message. Before uploading, verify that the declared type matches the file. See the [`anaconda channel upload`](/docs/cli-reference/anaconda-client/commands/channel-upload) reference. ## Before you begin 1. Install or update `anaconda-client` to version 1.15.0 or later: ```sh theme={null} conda install --name base "anaconda-client>=1.15.0" ``` 2. Log in to Anaconda: ```sh theme={null} anaconda login ``` ## Creating a private channel > [!NOTE] > > Private channels live under an [organization](/docs/anaconda-org/admin-guide/organizations) namespace. If you use your username as the namespace in the CLI, an organization is created for you automatically. On Anaconda.org, you must select an existing organization. See [Known limitations](#known-limitations) for additional restrictions. **CLI** To create a private channel, run: ```sh theme={null} anaconda channel create / --private ``` Comments Replace \ with the name of your organization or your username.\\ Replace \ with a name for your channel. For the full list of options, see the [`anaconda channel create`](/docs/cli-reference/anaconda-client/commands/channel-create) reference. **Anaconda.org** 1. Log in to [Anaconda.org](https://anaconda.org). 2. From the user menu, select **My Channels**. 3. Click **Create Channel**. 4. Under **Visibility**, select **Private**. 5. Open the **Location** dropdown. 6. Under **Organizations**, select the organization that will own the channel. 7. Click **Next**. 8. Enter a channel name and optional description. > [!NOTE] > > Channel names can contain only lowercase letters, numbers, and dashes. See [Known limitations](#known-limitations) for additional restrictions. 9. Click **Complete** to create your channel. ## Uploading packages To upload packages to your private channel, run: ```sh theme={null} anaconda channel upload --channel / ``` Comments Replace \ with the path to one or more package files (glob patterns like `*.conda` are supported).\\ Replace \ with the name of your organization.\\ Replace \ with the name of your channel. > [!WARNING] > > Do not mix conda packages and Python wheel packages in the same channel. Mixing package types in a single channel can cause dependency resolution failures during installation. Create separate channels for conda packages and wheel packages. For the full list of options, see the [`anaconda channel upload`](/docs/cli-reference/anaconda-client/commands/channel-upload) reference. ## Sharing a channel Access to a private channel is not automatic. Organization membership alone does not grant channel access. You must explicitly share the channel with each collaborator. > [!NOTE] > > During the beta, channel sharing is available through the CLI only and only two additional collaborators are allowed per private channel. See [Known limitations](#known-limitations) for additional restrictions. To share a channel with a user, run: ```sh theme={null} anaconda channel share --channel / ``` Comments Replace \ with the user's email address or username.\\ Replace \ with the name of your organization.\\ Replace \ with the name of your channel. By default, shared users receive **viewer** (read-only) access. To grant write access so a collaborator can upload packages, specify the `--role` option: ```sh theme={null} anaconda channel share --channel / --role collaborator ``` Comments Replace \ with the user's email address or username.\\ Replace \ with the name of your organization.\\ Replace \ with the name of your channel. Collaborators receive an email notification when you share a channel with them. ### Revoking access To revoke a user's access to a channel, use the `--unshare` flag: ```sh theme={null} anaconda channel share --channel / --unshare ``` Comments Replace \ with the user's email address or username.\\ Replace \ with the name of your organization.\\ Replace \ with the name of your channel. ### Roles Role Description `viewer` Read-only access. The user can view and install packages from the channel. `collaborator` Read and write access. The user can view, install, and upload packages to the channel. For the full list of options, see the [`anaconda channel share`](/docs/cli-reference/anaconda-client/commands/channel-share) reference. ## Managing channels ### Listing your channels You can view your channels from the CLI or on Anaconda.org. > [!NOTE] > > During the beta, the Anaconda.org view is read-only and does not support filtering. See [Known limitations](#known-limitations) for additional restrictions. **CLI** To see all channels you own or have access to, run: ```sh theme={null} anaconda channel list ``` This displays both public and private channels across Anaconda.org and Anaconda.com. To view only your Anaconda.org channels, filter by source: ```sh theme={null} anaconda channel list --source org ``` For the full list of options, see the [`anaconda channel list`](/docs/cli-reference/anaconda-client/commands/channel-list) reference. **Anaconda.org** 1. Log in to [Anaconda.org](https://anaconda.org). 2. Click the user dropdown menu. 3. Select *My Channels*. The **My Channels** page lists all channels you own, including both public and private channels. Click a channel name to view its overview page. ### Viewing channel details The CLI provides the most complete channel information during the beta. The Anaconda.org overview page shows basic details only. **CLI** To display information about a specific channel, including its privacy setting, artifact count, and download count, run: ```sh theme={null} anaconda channel show / ``` Comments Replace \ with the name of your organization.\\ Replace \ with the name of your channel. For the full list of options, see the [`anaconda channel show`](/docs/cli-reference/anaconda-client/commands/channel-show) reference. **Anaconda.org** The channel overview page displays summary information about a channel, including its name, privacy setting, and package contents. To view a channel's overview page, click the channel name from the **My Channels** page. > [!NOTE] > > During the beta, the channel overview page shows the overview tab only. Package details and collaborator access management are not available from the web interface. See [Known limitations](#known-limitations) for additional restrictions. ### Changing channel privacy To switch a channel between public and private, run: ```sh theme={null} anaconda channel modify / --privacy ``` Comments Replace \ with the name of your organization.\\ Replace \ with the name of your channel.\\ Replace \ with `public` or `private`. For the full list of options, see the [`anaconda channel modify`](/docs/cli-reference/anaconda-client/commands/channel-modify) reference. ### Removing a channel To permanently remove a channel and all of its packages, run: ```sh theme={null} anaconda channel remove / ``` Comments Replace \ with the name of your organization.\\ Replace \ with the name of your channel. > [!WARNING] > > Removing a channel deletes all packages and artifacts in that channel. This action cannot be undone. Only channel owners can remove a channel or delete a package from a channel. For the full list of options, see the [`anaconda channel remove`](/docs/cli-reference/anaconda-client/commands/channel-remove) reference. ## Installing packages from a private channel Before you can install packages from a private channel, you must be logged in to Anaconda and have been granted access to the channel: ```sh theme={null} anaconda login ``` ### Configuring conda for private channels During the beta, you must add the following to your `.condarc` file to enable authentication for private channels: ```yaml theme={null} channel_settings: - channel: https://repo.anaconda.cloud/* auth: anaconda-auth auth_domain: anaconda.com credential_type: api-key ``` See [Known limitations](#known-limitations) for additional restrictions. ### Installing a package To install a package from your private channel, run: ```sh theme={null} conda install --channel https://repo.anaconda.cloud// ``` Comments Replace \ with the name of the organization that owns the channel.\\ Replace \ with the name of the channel.\\ Replace \ with the name of the package you want to install. If your private channel contains a package that also exists on a default channel (such as `main`) and you want to force installation from the private channel, add the `--override-channels` flag: ```sh theme={null} conda install --channel https://repo.anaconda.cloud// --override-channels ``` Comments Replace \ with the name of the organization that owns the channel.\\ Replace \ with the name of the channel.\\ Replace \ with the name of the package you want to install. The `--override-channels` flag is not necessary when installing custom packages that only exist in a private channel. # Anaconda.org release notes Source: https://anaconda.com/docs/anaconda-org/release-notes This page contains release notes for [Anaconda.org](/docs/anaconda-org/release-notes). For release notes for the Anaconda Client command line interface (CLI) tool, see the [Anaconda Client changelog](/docs/cli-reference/anaconda-client/release-notes). **1.0.39/4.2.30** 2026-10-22 **Improvements** * Updated install instructions on namespaced (private or public) channel details pages to correctly explain how to install packages from them. **1.0.38/4.2.30** 2026-10-13 **Improvements** * Channel creation failure notifications now display the specific error message returned by the API, so you can see why creation failed. * When creating a channel, the namespace selector now explains why a username is unavailable (for example, if it is reserved or already in use). Users without an organization see a clear message instead of an empty selector. * Model column titles that are too long for their column now display a tooltip with the full text on hover. * The quantization file dropdown on model detail pages now follows the same conventions as the file dropdown on package detail pages. * Improved the layout of model detail pages on mobile devices. **Bug fixes** * Fixed an issue where the **Files** tab on conda-pypi package pages displayed file sizes as "NaN undefined" instead of the actual size. * Fixed an issue where download counts appeared on search result cards for channels that do not track downloads. **1.0.36/4.2.29** 2026-10-08 **Improvements** * Security improvements related to organization permissions. **1.0.36/4.2.26** 2026-09-30 **What's new** * Added a **Models** tab to search results, enabling users to browse Anaconda's curated model catalog alongside packages and environments. Model cards display the model name, publisher, model type, parameter count, size, max RAM usage, and tags. * Added model detail pages with metadata, licensing information, training provenance, and benchmark scores. Signed-in users can view full evaluation scores and install compatible models through Anaconda Desktop. * Added support for private channels. Users with an organization can create private channels that are only accessible to authorized collaborators. * Added a **My Channels** page where users can view and manage their channels, accessible from the user dropdown menu. * Added a [channel homepage](https://anaconda.org/channels/conda-pypi) and individual package detail pages for the conda-pypi channel, which indexes pure Python wheels from PyPI. **1.0.35/4.2.26** 2026-09-17 **What's new** * Added `llms.txt` and `llms-full.txt` files at the site root for AI agents and LLM tools to discover Anaconda.org content and URL patterns. * Channel and package pages now return Markdown when a request includes the `Accept: text/markdown` header. AI agents and LLM tools can retrieve package details from the same URL a browser uses, without running JavaScript. For example: `curl https://anaconda.org/channels/main/packages/fastapi/overview -H "Accept: text/markdown"` * Added a **Service Status** link to the site footer, linking to the Anaconda status page. **Improvements** * Improved the reliability of package download statistics by resolving database connection timeouts that could cause 500 errors on package detail pages. * Added an API endpoint for querying the full list of labels for a channel (`GET /channels//labels`). **1.0.34/4.2.23** 2026-08-04 **Bug Fixes** * Fixed an issue where the Environments tab displayed a blank page instead of a "no results" message when a search returned no environments. * Fixed a mislabeled column header in environment search results. It now correctly reads "Summary" instead of "Description". * Removed misleading clickable styling from the **Channel** and **Tags** values in an environment's **About** section, since they aren't interactive. * Fixed an issue in the Try This Package editor where clicking **Reset** after saving custom code would revert to an older saved version instead of the most recent one. * Released the `main-x` channel as general availability and removed its beta status. The `main-x` channel now contains thousands of new conda packages built by Anaconda and is meant to be used alongside the `main` channel. * Corrected the `main-x` installation command to match the latest recommended configuration steps. **1.0.32/4.2.23** 2026-07-28 **What's new** * Added an **Install via Desktop** button to all package details pages. Click to install the package to an environment of your choice in Anaconda Desktop. * Added a package comparison mode to enable users to compare up to five packages side-by side by download counts, last update date, compatible platforms, and more. **1.0.30/4.2.23** 2026-07-21 **What's new** * Added Anaconda-curated, pre-made environments that users can search for, download, and install. **1.0.29/4.2.23** 2026-07-13 **What's new** * Added a new Try This Package beta feature to some package details pages, which enables users to run code snippets involving the package directly in the browser. * Added a temporary banner to advertise a paid research study on Python environments and performance. **Improvements** * Added improvements for package download counts to improve accuracy. **Bug Fixes** * `notices.json` links now properly redirect for URL links containing `/c/` , `/channel/`, and `/label/