Xonsh Installation Guide¶

The guide is new so in case of error please open the issue in the tracker.

Before Installing¶

Xonsh is a full-featured shell and can technically be used as a login shell, but since it is not a POSIX‑compatible shell, we don’t recommend doing so unless you clearly understand the purpose and consequences. Do not attempt to set it as your default shell using chsh or by any other method that would replace the system shell.

The recommended practice is to create a Xonsh profile in your terminal emulator.

Overview¶

Xonsh is a Python-based shell that requires Python to be packaged, preinstalled or compiled in order to run. Since there are many ways to install Python, there are also many ways to run xonsh. The table describes the main approaches and their advantages.

	Use as core shell	Isolated env	Fresh version	Automation	Portable
Independent install	🟢	🟢	🟢	◯
Package			🟢	🟢
AppImage		🟢	🟢	◯	🟢
Container		🟢	🟢	🟢
System package			◯

Work in progress: binary build, running in RustPython, xonsh Flatpak. Check out Nightly build page.

Independent install¶

When xonsh is used as a core shell, it is necessary to keep the Python environment with xonsh stable, predictable, and independent of system changes. Lightweight environment managers such as venv, pipx, or rye do not fully address this requirement. Package managers that can install fully isolated Python environments as a core feature, such as Miniconda or Micromamba, should be used.

Linux / macOS / WSL¶

Install Xonsh independently using Micromamba:

$ TARGET_DIR=$HOME/.local/xonsh-env PYTHON_VER=3.11 XONSH_VER='xonsh[full]' \
  /bin/bash -c "$(curl -fsSL https://xon.sh/install/mamba-install-xonsh.sh)"

Learn more: Mamba installer.

Windows¶

Note

The installation instructions for Windows were recently updated. If you run into any issues, please report them to the issue tracker.

We provide an experimental Xonsh installer for Windows (no admin rights required). Download the .exe from the Xonsh WinGet releases page:

inno6 — for Windows 10/11 (latest Python 3).
inno5 — for Windows 8.1+ (pinned to Python 3.13).

Or install via the script (no admin rights required):

> curl -L -o install_xonsh.cmd https://xon.sh/install/windows_install_xonsh.cmd
> install_xonsh.cmd  # Install to ~/xonsh-env/

Package¶

pip:

You can install the xonsh package from PyPI with any pip-compatible installer (pip, pipx, uv, rye, poetry, etc.).

$ pip install 'xonsh[full]'

Pip can also install the most recent xonsh source code from the xonsh project repository:

$ pip install 'https://github.com/xonsh/xonsh/archive/main.zip#egg=xonsh[full]'

mamba:

$ mamba install xonsh

conda:

$ conda config --add channels conda-forge
$ conda install xonsh

AppImage¶

Xonsh is available as a single AppImage bundled with Python, allowing you to run it on Linux without installation:

$ wget 'https://github.com/xonsh/xonsh/releases/latest/download/xonsh-x86_64.AppImage' -O xonsh
$ chmod +x xonsh
$ ./xonsh

Study how to package your libraries in Xonsh AppImage article.

Container¶

Xonsh publishes a handful of containers, primarily targeting CI and automation use cases. All of them are published on Docker Hub.

Example of running an interactive xonsh session in a container:

$ docker run --rm -it xonsh/interactive

Learn more: Containers.

System package¶

Various operating system distributions provide platform-specific package managers that may offer a xonsh package. This approach is not recommended for the following reasons:

On non-rolling-release operating systems, the xonsh version is often outdated.
The package may be missing important dependencies.
System package managers install xonsh into the system Python environment, which means that any significant system update or change has a high probability of breaking the shell.

Arch Linux:

$ pacman -S xonsh  # not recommended but possible

Debian/Ubuntu:

$ apt install xonsh  # not recommended but possible

Fedora:

$ dnf install xonsh  # not recommended but possible

GNU guix:

$ guix install xonsh  # not recommended but possible

macOS:

$ brew install xonsh  # not recommended but possible

WIP Binary build¶

Using Nuitka (a Python compiler), it is possible to build a binary version of xonsh. Learn more in xonsh/2895.

WIP RustPython build¶

Using RustPython (a Python Interpreter written in Rust), it is possible to run xonsh using Rust. Learn more in xonsh/5082.

Updating xonsh¶

How you update xonsh depends on the install method.

xonsh installed via pip

If xonsh was installed via pip (possibly into a virtual environment), you can update it from within xonsh itself using xpip — a predefined alias pointing to the pip command associated with the Python executable that runs the current xonsh session:

@ xpip install --upgrade xonsh  # install the latest release
@ xpip install -U --force-reinstall git+https://github.com/xonsh/xonsh  # install from the repository

On Windows the running xonsh.exe is locked by the OS, so pip cannot replace it from inside xonsh itself. Grab the interpreter path with xcontext, leave the shell, then run pip from another terminal (cmd, PowerShell, etc.):

@ xcontext            # note the "xpython" path
@ exit                # release the lock on xonsh.exe
> <xpython> -m pip install --upgrade xonsh

xonsh installed via a package manager

If you installed xonsh via a package manager, it is recommended to update it through the package manager’s appropriate command. For example, on macOS with homebrew:

$ brew upgrade xonsh

Setting xonsh as the default shell¶

Setting xonsh as your default login shell is not recommended. Xonsh is a full-featured shell and can technically be used as a login shell, but since it is not POSIX-compatible, system scripts and tooling that expect a POSIX shell may misbehave. Use it only if you clearly understand the purpose and consequences — see the rationale in Before Installing above. The recommended practice is to create a xonsh profile in your terminal emulator instead.

If you still want to use xonsh as your default shell, you will have to add xonsh to /etc/shells and switch:

$ which xonsh
# which xonsh >> /etc/shells
$ chsh -s $(which xonsh)

You will have to log out and log back in before the changes take effect.