Antigen v2.3.0: the zsh bundle manager returns after a release gap from 2018 to 2026

Bundles declared in .zshrc, applied once at the end

Antigen is a small set of zsh functions that manage plugins, which it calls bundles. The model is borrowed from vim: Antigen is to zsh what Vundle is to vim. You list bundles in .zshrc and finish with a single apply call. A typical file looks like this:

source /path-to-antigen/antigen.zsh

# Load the oh-my-zsh's library.
antigen use oh-my-zsh

# Bundles from the default repo (robbyrussell's oh-my-zsh).
antigen bundle git
antigen bundle heroku
antigen bundle pip
antigen bundle lein
antigen bundle command-not-found

# Syntax highlighting bundle.
antigen bundle zsh-users/zsh-syntax-highlighting

# Load the theme.
antigen theme robbyrussell

# Tell Antigen that you're done.
antigen apply

Short names such as git or pip resolve against the default repository, robbyrussell's oh-my-zsh, while an owner/name pair such as zsh-users/zsh-syntax-highlighting pulls from that GitHub repository directly. The first time you open zsh with this file, the declared bundles get installed. The full syntax of antigen bundle is on the Commands wiki page, not in the repository itself.

Why it exists: oh-my-zsh as one giant repository

Antigen started as a reaction to how oh-my-zsh bundles many plugins from many authors in a single repository, which the author argues does not scale and puts a heavy review load on robbyrussell. Several oh-my-zsh issues (465, 377 and 1014) discussed better plugin management without progress, and Antigen was the attempt to move it forward.

The practical result is that you are not limited to plugins inside the oh-my-zsh repository, and you do not need to keep your own fork and pull from upstream. The project openly encourages grabbing plugins straight from their authors before they are ever submitted to oh-my-zsh. The trade-off is yours to manage: code from many individual repositories means many individual authors you are trusting in your shell startup.

One curl line, and the nightly is one URL away

Installation is a single file download:

curl -L git.io/antigen > antigen.zsh
# or use git.io/antigen-nightly for the latest version

The stable link and the nightly link differ by one word, so it is easy to end up on the wrong one by copying a snippet from someone else's dotfiles. The repository has a VERSION file and a CHANGELOG.md; compare what you downloaded against them. System package manager installs exist, but they are covered on the Installation wiki page rather than in the main page, so the version a distribution ships is a separate thing to check. Antigen requires zsh 4.3.11 or later.

Releases jumped from v2.2.3 in 2018 to v2.3.0 in 2026

The release history has a long gap. v2.2.2 shipped on 2017-11-20, v2.2.3 on 2018-01-04, and the next release, v2.3.0, arrived on 2026-10-09. The last push to the repository was on 2026-10-09, and the default branch is develop rather than main or master. The repository is not archived.

Parts of the front page have not caught up. The status badges still link to travis-ci.org, and the text says Antigen has been used in the wild for around a couple of years. If you are coming back to Antigen after years on v2.2.3, read CHANGELOG.md for the v2.3.0 changes before upgrading a working setup, and keep the old antigen.zsh around so you can roll back by restoring a single file.

Theme switching only lasts for the session

Antigen can change the prompt theme with one command:

antigen theme candy

The change applies only to the current session. Open a new terminal and you are back to whatever theme .zshrc sets, unless you write the line into .zshrc yourself. That makes antigen theme useful for trying themes interactively, but it is not a settings store; Antigen keeps no separate state for your choice. The Show off wiki page covers interactive use, and the In the wild page collects more configuration examples.

The shipped file is assembled by configure and a Makefile

antigen.zsh is not hand-written as one file. A configure script generates a Makefile with seven feature switches: WITH_LOCK, WITH_DEFER, WITH_CACHE, WITH_DEBUG, WITH_PARALLEL, WITH_EXTENSIONS and WITH_COMPLETION, all set to yes in the committed Makefile. Each switch pulls in a file from src/ext, such as ext.zsh, defer.zsh, lock.zsh, parallel.zsh and cache.zsh; WITH_CACHE also adds src/boot.zsh, and WITH_COMPLETION adds src/_antigen. The rest is concatenated from src/antigen.zsh, src/helpers, src/lib and src/commands into the target bin/antigen.zsh, with PREFIX defaulting to /usr/local.

Tests use cram with CRAM_OPTS set to -v and run in a Docker container from the desyncr/zsh-docker- image, with ZSH_VERSION defaulting to zsh-5.3. If you patch Antigen, edit the files under src and rebuild; the generated Makefile warns not to edit it directly.

Editorial conclusion

Antigen fits zsh users who want a Vundle-like list of bundles in .zshrc, mixing oh-my-zsh plugins with plugins pulled straight from their authors' GitHub repositories, on zsh 4.3.11 or newer. It is a weaker choice if you need documentation that ships with the code, since commands and configuration live on the GitHub wiki. Before switching, check which version the git.io/antigen download actually gives you against the VERSION file and the v2.3.0 release, because the previous release before that was v2.2.3 from January 2018.

Frequently asked questions

Official sources

1. License: MIT
2. Project website
3. README
4. Releases
5. zsh-users/antigen on GitHub