UVX(1)

📦 version 0.11.20, in ubuntu stonking

okay so bestie, welcome to the manual page for uvx — it lives in section 1, User Commands, and it's about to become your whole personality 🫶

🌸 NAME 🌸

uvx — run commands in isolated Python environments ✨

🦋 SYNOPSIS 🦋

uvx [OPTIONS] [COMMAND]

💖 DESCRIPTION 💖

Run a command provided by a Python package. That's it, that's the whole vibe. You point it at a package, it spins up a lil isolated world, and the command just runs. No cap. 👑

👑 OPTIONS 👑

✨ the main-character options ✨

  • --from <FROM> — use this package to provide the command you want 💫
  • -w, --with <WITH> — run with these packages installed too
  • --with-editable <WITH_EDITABLE> — same energy but the packages get installed in editable mode
  • --with-requirements <WITH_REQUIREMENTS> — run with whatever packages are listed in the files you hand over
  • -c, --constraints <CONSTRAINTS> — pin versions down using the given requirements files [env: UV_CONSTRAINT=]
  • -b, --build-constraints <BUILD_CONSTRAINTS> — constrain the build dependencies with the given requirements files when building source distributions [env: UV_BUILD_CONSTRAINT=]
  • --overrides <OVERRIDES> — override versions using the given requirements files [env: UV_OVERRIDE=]
  • --isolated — run the tool in its own isolated virtual environment, ignoring any tools you already have installed (fr, a fresh start) [env: UV_ISOLATED=]
  • --env-file <ENV_FILE> — load environment variables from a .env file [env: UV_ENV_FILE=]
  • --no-env-file — do NOT read environment variables from a .env file, we're not doing that today 🙈 [env: UV_NO_ENV_FILE=]
  • --lfs — whether to use Git LFS when adding a dependency from Git
  • --python-platform <PYTHON_PLATFORM> — the platform you're installing requirements for [possible values: windows, linux, macos, x86_64-pc-windows-msvc, aarch64-pc-windows-msvc, i686-pc-windows-msvc, x86_64-unknown-linux-gnu, aarch64-apple-darwin, x86_64-apple-darwin, aarch64-unknown-linux-gnu, aarch64-unknown-linux-musl, x86_64-unknown-linux-musl, riscv64-unknown-linux, x86_64-manylinux2014, x86_64-manylinux_2_17, x86_64-manylinux_2_28, x86_64-manylinux_2_31, x86_64-manylinux_2_32, x86_64-manylinux_2_33, x86_64-manylinux_2_34, x86_64-manylinux_2_35, x86_64-manylinux_2_36, x86_64-manylinux_2_37, x86_64-manylinux_2_38, x86_64-manylinux_2_39, x86_64-manylinux_2_40, aarch64-manylinux2014, aarch64-manylinux_2_17, aarch64-manylinux_2_28, aarch64-manylinux_2_31, aarch64-manylinux_2_32, aarch64-manylinux_2_33, aarch64-manylinux_2_34, aarch64-manylinux_2_35, aarch64-manylinux_2_36, aarch64-manylinux_2_37, aarch64-manylinux_2_38, aarch64-manylinux_2_39, aarch64-manylinux_2_40, aarch64-linux-android, x86_64-linux-android, wasm32-pyodide2024, wasm32-pyodide2025, arm64-apple-ios, arm64-apple-ios-simulator, x86_64-apple-ios-simulator]
  • --torch-backend <TORCH_BACKEND> — the backend to use when fetching packages in the PyTorch ecosystem (e.g., cpu, cu126, or auto) [env: UV_TORCH_BACKEND=] [possible values: auto, cpu, cu130, cu129, cu128, cu126, cu125, cu124, cu123, cu122, cu121, cu120, cu118, cu117, cu116, cu115, cu114, cu113, cu112, cu111, cu110, cu102, cu101, cu100, cu92, cu91, cu90, cu80, rocm7.2, rocm7.1, rocm7.0, rocm6.4, rocm6.3, rocm6.2.4, rocm6.2, rocm6.1, rocm6.0, rocm5.7, rocm5.6, rocm5.5, rocm5.4.2, rocm5.4, rocm5.3, rocm5.2, rocm5.1.1, rocm4.2, rocm4.1, rocm4.0.1, xpu]
  • -V, --version — display the uvx version 🎀

🔍 Index options 🔍

  • --index <INDEX> — the URLs to use when resolving dependencies, on top of the default index [env: UV_INDEX]
  • --default-index <DEFAULT_INDEX> — the URL of the default package index (by default: <https://pypi.org/simple>) [env: UV_DEFAULT_INDEX]
  • -i, --index-url <INDEX_URL> — (Deprecated: use --default-index instead) the URL of the Python package index (by default: <https://pypi.org/simple>) [env: UV_INDEX_URL]
  • --extra-index-url <EXTRA_INDEX_URL> — (Deprecated: use --index instead) extra URLs of package indexes to use, on top of --index-url [env: UV_EXTRA_INDEX_URL]
  • -f, --find-links <FIND_LINKS> — locations to search for candidate distributions, on top of whatever the registry indexes turn up [env: UV_FIND_LINKS]
  • --no-index — ignore the registry index (e.g., PyPI) entirely and just vibe with direct URL dependencies and the ones you gave via --find-links
  • --index-strategy <INDEX_STRATEGY> — the strategy to use when resolving against multiple index URLs [env: UV_INDEX_STRATEGY=] [possible values: first-index, unsafe-first-match, unsafe-best-match]
  • --keyring-provider <KEYRING_PROVIDER> — try to use keyring for authentication for index URLs [env: UV_KEYRING_PROVIDER=] [possible values: disabled, subprocess]

🧚 Resolver options 🧚

  • -U, --upgrade — allow package upgrades, ignoring pinned versions in any existing output file. Implies --refresh
  • -P, --upgrade-package <UPGRADE_PACKAGE> — allow upgrades for one specific package, ignoring pinned versions in any existing output file. Implies --refresh-package
  • --upgrade-group <UPGRADE_GROUP> — allow upgrades for every package in a dependency group, ignoring pinned versions in any existing output file
  • --resolution <RESOLUTION> — the strategy to use when picking between different compatible versions for a given package requirement [env: UV_RESOLUTION=] [possible values: highest, lowest, lowest-direct]
  • --prerelease <PRERELEASE> — the strategy to use when considering pre-release versions [env: UV_PRERELEASE=] [possible values: disallow, allow, if-necessary, explicit, if-necessary-or-explicit]
  • --fork-strategy <FORK_STRATEGY> — the strategy to use when selecting multiple versions of a given package across Python versions and platforms [env: UV_FORK_STRATEGY=] [possible values: fewest, requires-python]
  • --exclude-newer <EXCLUDE_NEWER> — limit candidate packages to the ones uploaded before the given date ⏰ [env: UV_EXCLUDE_NEWER=]
  • --exclude-newer-package <EXCLUDE_NEWER_PACKAGE> — limit candidate packages, but only for specific packages, to the ones uploaded before the given date
  • --no-sources — ignore the tool.uv.sources table when resolving dependencies. Used to lock against the standards-compliant, publishable package metadata, instead of using any workspace, Git, URL, or local path sources [env: UV_NO_SOURCES=]
  • --no-sources-package <NO_SOURCES_PACKAGE> — don't use sources from the tool.uv.sources table for the packages you specify [env: UV_NO_SOURCES_PACKAGE=]

💅 Installer options 💅

  • --reinstall — reinstall everything, no matter if it's already installed. Implies --refresh
  • --reinstall-package <REINSTALL_PACKAGE> — reinstall one specific package, no matter if it's already installed. Implies --refresh-package
  • --link-mode <LINK_MODE> — the method to use when installing packages from the global cache [env: UV_LINK_MODE=] [possible values: clone, copy, hardlink, symlink]
  • --compile-bytecode — compile Python files to bytecode after installation [env: UV_COMPILE_BYTECODE=]

🔥 Build options 🔥

  • -C, --config-setting <CONFIG_SETTING> — settings to pass to the PEP 517 build backend, written as KEY=VALUE pairs
  • --config-settings-package <CONFIG_SETTINGS_PACKAGE> — settings to pass to the PEP 517 build backend for one specific package, written as PACKAGE:KEY=VALUE pairs
  • --no-build-isolation — disable isolation when building source distributions [env: UV_NO_BUILD_ISOLATION=]
  • --no-build-isolation-package <NO_BUILD_ISOLATION_PACKAGE> — disable isolation when building source distributions for one specific package
  • --no-build — don't build source distributions [env: UV_NO_BUILD=]
  • --no-build-package <NO_BUILD_PACKAGE> — don't build source distributions for one specific package [env: UV_NO_BUILD_PACKAGE=]
  • --no-binary — don't install pre-built wheels [env: UV_NO_BINARY=]
  • --no-binary-package <NO_BINARY_PACKAGE> — don't install pre-built wheels for one specific package [env: UV_NO_BINARY_PACKAGE=]

🍓 Cache options 🍓

  • -n, --no-cache — avoid reading from or writing to the cache, and use a temporary directory for the duration of the operation instead [env: UV_NO_CACHE=]
  • --cache-dir <CACHE_DIR> — path to the cache directory [env: UV_CACHE_DIR=]
  • --refresh — refresh all cached data 🔄
  • --refresh-package <REFRESH_PACKAGE> — refresh cached data for one specific package

🐍 Python options 🐍

  • -p, --python <PYTHON> — the Python interpreter to use to build the run environment. [env: UV_PYTHON=]
  • --managed-python — require use of uv-managed Python versions [env: UV_MANAGED_PYTHON=]
  • --no-managed-python — disable use of uv-managed Python versions [env: UV_NO_MANAGED_PYTHON=]
  • --no-python-downloads — disable automatic downloads of Python. [env: "UV_PYTHON_DOWNLOADS=never"]

🌈 Global options 🌈

  • -q, --quiet... — use quiet output 🤫
  • -v, --verbose... — use verbose output 🗣️
  • --color <COLOR_CHOICE> — control the use of color in output [possible values: auto, always, never]
  • --system-certs — whether to load TLS certificates from the platform's native certificate store [env: UV_SYSTEM_CERTS=]
  • --offline — disable network access [env: UV_OFFLINE=]
  • --allow-insecure-host <ALLOW_INSECURE_HOST> — allow insecure connections to a host [env: UV_INSECURE_HOST=]
bestie, that one's literally named "insecure", so like… be aware, okay? 🙈
  • --no-progress — hide all progress outputs [env: UV_NO_PROGRESS=]
  • --directory <DIRECTORY> — change to the given directory before running the command [env: UV_WORKING_DIR=]
  • --project <PROJECT> — discover a project in the given directory [env: UV_PROJECT=]
  • --config-file <CONFIG_FILE> — the path to a uv.toml file to use for configuration [env: UV_CONFIG_FILE=]
  • --no-config — avoid discovering configuration files (pyproject.toml, uv.toml) [env: UV_NO_CONFIG=]
  • -h, --help — display the concise help for this command

Use uv help tool run for more details.

and that's the whole page, bestie, you ate that 💅 this was uvx version 0.11.20+ds, dated August 2026 — go be iconic with it 🎀✨🦋

📦 where this page comes from