conda-global
Global tool installation for conda — install CLI tools into isolated environments and make them available on PATH via trampolines.
Overview
conda-global lets you install command-line tools (like gh, ruff, bat) into
isolated conda environments and expose them on your PATH without polluting any
project environment. It works like pipx for Python tools or pixi global for
the pixi ecosystem, but for the entire conda package ecosystem.
For one-off command execution without installing a persistent PATH tool, use
conda-exec, installed
separately with conda install -c conda-forge conda-exec:
conda exec ruff check .
Quick start
# Install a tool
conda global install gh
# Use it from anywhere
gh --version
# List installed tools
conda global list
# Update all tools
conda global update
# Remove a tool
conda global uninstall gh
How it works
Each tool gets its own isolated conda environment. A small Rust trampoline
binary (provided by the conda-trampoline
package) acts as a launcher — it reads a JSON config, sets up the environment,
and launches the real binary with zero activation overhead.
The manifest lives at ~/.conda/global.toml; environments and trampolines
live under ~/.conda/global/. See the
docs for details.
Installation
conda install -c conda-forge conda-global
Then add the bin directory to your PATH:
conda global ensurepath
Commands
| Command | Description |
|---|---|
conda global install <pkg> |
Install a tool into an isolated environment |
conda global uninstall <env> |
Remove a tool and its environment |
conda global add <pkg> -e <env> |
Add a dependency to an existing tool env |
conda global remove <pkg> -e <env> |
Remove a dependency from a tool env |
conda global list |
List installed tools |
conda global update [-e <env>] |
Update one or all tools |
conda global sync |
Reconcile filesystem with manifest |
conda global expose <name>=<bin> -e <env> |
Expose a binary on PATH |
conda global hide <name> -e <env> |
Remove a binary from PATH |
conda global tree -e <env> |
Show dependency tree |
conda global pin -e <env> |
Prevent upgrades |
conda global unpin -e <env> |
Allow upgrades |
conda global ensurepath |
Add bin directory to PATH |
conda global edit |
Edit global.toml |
A standalone cg alias is also available (cg install ruff, etc.).
License
BSD-3-Clause
Metadata
Release files for conda-global 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| conda_global-0.2.0.tar.gz | 6.1 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| conda_global-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.2 MB
Release files / conda_global-0.2.0.tar.gz
| Download URL | conda_global-0.2.0.tar.gz |
|---|---|
| Size | 6.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da2f2bb330a2cae376c951e20b8968365cef850a6518d0326af980a906b21f58
|
|
BLAKE2b-256 checksum How to use checksums |
d83006554a08cdf5b43e722602de30509a2b85f04f03069e063f6efe0c656fcc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 22, 2026.
Transparency logRelease files / conda_global-0.2.0-py3-none-any.whl
| Download URL | conda_global-0.2.0-py3-none-any.whl |
|---|---|
| Size | 26.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a7d998f986cf31fa9b9f8d12f2ae8757018e0f9462790904d87f5a0d19593baf
|
|
BLAKE2b-256 checksum How to use checksums |
9de86cd4e0f9b092f4d69ec1c786a4e389a2fbc8befc9e7e1aac1f7b611ab603
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 22, 2026.
Transparency log