Skip to main content
The pixi.toml manifest file is the heart of a pixi workspace. It defines workspaces, packages, dependencies, tasks, environments, and more.

Overview

A pixi.toml manifest must have one of:
  • [workspace] - For workspace definitions
  • [project] - For workspace definitions (alias for [workspace])
  • [package] - For buildable packages

Schema Validation

Add schema validation to your pixi.toml:
This enables autocompletion and validation in editors that support JSON schemas.

Workspace Configuration

[workspace]

Defines a pixi workspace (also available as [project]).
string
required
The name of the workspace.
string
The version of the workspace. Should follow SemVer.
string
A short description of the workspace.
array
List of workspace authors in “Name <email>” format.
array
required
Conda channels to use for dependency resolution.
With priorities:
array
required
Target platforms for the workspace.Valid platforms:
  • linux-64, linux-32, linux-aarch64, linux-armv6l, linux-armv7l, linux-ppc64, linux-ppc64le, linux-riscv32, linux-riscv64, linux-s390x
  • osx-64, osx-arm64
  • win-64, win-32, win-arm64
  • emscripten-wasm32, wasi-wasm32
  • noarch
string
License identifier (SPDX format recommended).
path
Path to the license file.
path
Path to the README file.
url
Homepage URL.
url
Repository URL.
url
Documentation URL.

Dependencies

[dependencies]

Conda dependencies for the default environment.
Available fields:
  • version - Version constraint (MatchSpec format)
  • channel - Override channel for this package
  • build - Build string constraint
  • build-number - Build number constraint
  • file-name - Exact file name
  • subdir - Platform subdirectory
  • md5 / sha256 - Hash verification
  • path - Local package path
  • url - Package URL
  • git - Git repository URL
  • branch / tag / rev - Git reference

[pypi-dependencies]

PyPI dependencies installed with pip.
Follows PEP 440 version specifiers.

[host-dependencies] and [build-dependencies]

Dependencies for building packages. See Build System documentation.

[dev]

Source packages whose dependencies should be installed without building the package itself.

Tasks

[tasks]

Define tasks that can be run with pixi run.
string | array
Command to execute. Can be a string or array of commands.
path
Working directory for the task.
array
Tasks that must run before this task.
With arguments:
object
Environment variables to set.
boolean
default:"false"
Run in a clean environment (only pixi-set variables).
array
Task arguments that can be passed from the command line.

Environments

[environments]

Define multiple environments with different feature combinations.
array
Features to include in this environment.
string
Solve multiple environments together to share dependencies.
boolean
default:"false"
Exclude the default feature from this environment.

Features

[feature.<name>]

Define features that can be composed into environments.
Features can have:
  • dependencies - Conda dependencies
  • pypi-dependencies - PyPI dependencies
  • tasks - Feature-specific tasks
  • channels - Override channels
  • platforms - Supported platforms
  • system-requirements - Platform requirements
  • activation - Activation scripts/environment
  • target - Platform-specific configuration

See Next

  • pyproject.toml - Using pixi with Python projects
  • pixi.lock - Lock file format
  • [Build Configuration(/build/getting-started) - Building packages