CLI tool
XcodesOrg/xcodes avatar
XcodesOrg/xcodes

xcodes: the Apple ID prompt is the part to understand before you start

The best command-line tool to install and switch between multiple versions of Xcode.

4,893 stars194 forksSwiftMIT

At a glance

What is it?
Xcodes installs and switches between Xcode versions from the command line, and the interesting engineering is not the download but what happens around it: an Apple ID that goes into your keychain, a macOS administrator password at the last step, a six stage progress log, and an optional aria2 path that turns one connection into sixteen.
Who is it for?
Adopt xcodes if you keep several Xcode versions on a Mac, need arm64 or Intel specific builds, or want CI to pin a version through a `.xcode-version` file instead of whatever the machine happens to have. On a fresh machine with no Xcode at all, use the Homebrew or release builds rather than a source build, since that route needs Xcode 12.0 or later.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 4 days ago.
What is it written in?
Mainly Swift, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • XcodesOrg/xcodes4,893 ★ · +67
Star history
Repository2026-09-232026-11-15
XcodesOrg/xcodes4.8k4.9k

67 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Homebrew first, because those builds need no Xcode

The preferred install is one line:

sh
brew install xcodesorg/made/xcodes

The reason it is preferred is stated right after it: those are Developer ID signed and notarized release builds, and they do not require Xcode to already be installed in order to use. That is the whole point of the tool, since the thing being installed is normally the thing you need first. Other routes are documented too. Downloading the latest release from the Releases page gives you a Developer ID signed build with the same property, and Mint installs from source with `mint install XcodesOrg/xcodes`. The signing pipeline behind those binaries is in the Makefile, where the `sign` target runs `codesign` against a Developer ID Application identity with `--options runtime`, and `notarize` calls `./notarize.sh xcodes.zip` with a team id.

The source build is the only one that needs Xcode, and it fails in one specific way

Building from source requires Xcode 12.0 or later, so the README is blunt about the consequence: it is not an option for setting up a computer from scratch. The sequence is:

sh
git clone https://github.com/XcodesOrg/xcodes
cd xcodes
make install
# or, if /usr/local/ isn't in your PATH
PREFIX=/your/install/directory make install

The documented failure is worth knowing because it looks alarming:

sh
swift build
error: terminated(72): xcrun --sdk macosx --find xctest output:

That message means no Xcode version is selected yet. The fix is `xcode-select`, or choosing a Command Line Tools entry in the Locations tab of Xcode's preferences. The same circularity shows up in development: building and running xcodes requires Xcode 13, though the tool still runs normally inside Xcode itself, where you can build, run and test, and type your Apple ID or 2FA code straight into Xcode's console when it prompts.

Six steps, an admin password, and your Apple ID in the keychain

An install looks like this:

sh
(1/6) Downloading Xcode 11.2.0: 100%
(2/6) Unarchiving Xcode (This can take a while)
(3/6) Moving Xcode to /Applications/Xcode-11.2.0.app
(4/6) Moving Xcode archive Xcode-11.2.0.xip to the Trash
(5/6) Checking security assessment and code signing
(6/6) Finishing installation
xcodes requires superuser privileges in order to finish installation.
macOS User Password:

Xcode 11.2.0 has been installed to /Applications/Xcode-11.2.0.app

Two credentials are involved and they are not the same one. You are prompted for your Apple ID username and password, or you can pass `XCODES_USERNAME` and `XCODES_PASSWORD`, and after a successful authentication xcodes saves that password into the keychain and remembers the Apple ID for later runs. The macOS User Password prompt at step six is the administrator password, needed because xcodes requires superuser privileges to finish installation. The `signout` command clears the stored username and password, and setting `XCODES_USERNAME` switches to a different Apple ID.

aria2 turns one connection into sixteen, and the directory is yours to choose

If `aria2` is on the machine, xcodes picks it up automatically and uses up to 16 connections, which the README puts at 3 to 5x faster than URLSession for an Xcode download. The second decision is where the app goes. Xcode lands in /Applications by default, and `--directory` or `XCODES_DIRECTORY` puts it elsewhere, which matters for an external volume such as `xcodes install --latest --directory "/Volumes/Bag Of Holding/"`. Every command accepts it, `select` and `uninstall` included, so a machine can hold all of its Xcode versions in one directory instead of scattered through /Applications. Older archives can be reused instead of downloaded, since `xcodes install 9.0 --path ~/Archive/Xcode_9.xip` installs from a local file, and betas are addressable by name with `xcodes install 11 Beta 7`, `xcodes install 11.2 GM seed` or `xcodes install --latest-prerelease`.

Architecture filters are exact, and arm64 means Apple Silicon only

The `list` and `runtimes` commands show architecture availability when Apple provides it, labelling downloads `[Universal]`, `[Apple Silicon]` or `[Intel]`. The filters are strict rather than fuzzy, which is the detail to internalise: `--architecture arm64` and `--architecture appleSilicon` both return Apple Silicon only, `--architecture x86_64` returns Intel only, and `--architecture universal` returns the builds that do both. The option can be repeated:

sh
xcodes list --architecture arm64
xcodes list --architecture universal
xcodes runtimes --architecture arm64 --architecture universal --include-betas

Because the labels only appear when Apple publishes the information, an unlabelled entry in the list is not a claim that a build is universal; it is a claim that nobody said.

A .xcode-version file is how a team pins the toolchain

The recommendation for CI and for teams is a one line file in the repository:

txt
13.4.1

That declares the Xcode version explicitly instead of inheriting whatever the build machine happens to have selected, and the proposal for the file is written up in `XCODE_VERSION.md` at the repository root. It is the cheapest part of the tool to adopt and the one that pays off on every pipeline run. Two neighboring commands complete the version story: `select` changes the selected Xcode and `installed` lists what is on the machine, while `list` shows everything available and `update` refreshes that list, since Apple's catalogue changes independently of your checkout. Version numbers reach the tool itself through `xcodes version`, and the project is versioned in step with those releases: 2.0.2 on 2026-06-17, 2.0.3 on 2026-07-08 and 2.1.0 on 2026-09-14, the last one a login fix, with the last recorded push on the same day.

Runtimes have their own subcommand, unxip is experimental

Simulator runtimes are managed separately from Xcode itself:

sh
xcodes runtimes --include-betas

lists them, and `xcodes runtimes install "iOS 17.0-beta1"` installs one by name. Beta runtimes need the flag to appear at all. Unarchiving is the slow step in a fresh install, and the experimental option addresses it directly: `--experimental-unxip` can unxip up to 70% faster on some systems, credited to saagarjhi's unxip project, and it appears as `xcodes install --latest --experimental-unxip`. Shell completion is available too, generated with `--generate-completion-script`, so for zsh with oh-my-zsh:

sh
mkdir ~/.oh-my-zsh/completions
xcodes --generate-completion-script > ~/.oh-my-zsh/completions/_xcodes

Version selection is also a command rather than a guess: `xcodes select` changes which Xcode is active.

Editorial conclusion

Adopt xcodes if you keep several Xcode versions on a Mac, need arm64 or Intel specific builds, or want CI to pin a version through a `.xcode-version` file instead of whatever the machine happens to have. On a fresh machine with no Xcode at all, use the Homebrew or release builds rather than a source build, since that route needs Xcode 12.0 or later. Verify first which architectures you need and whether aria2 is installed, because that changes the download path, and read `signout` before you care about a stored Apple ID.

Frequently asked questions

How do I install xcodes?

Homebrew is the preferred route, brew install xcodesorg/made/xcodes, and those are Developer ID signed and notarized builds that do not need Xcode present. You can also download a release from the Releases page, install with mint install XcodesOrg/xcodes, or build from source with make install, which requires Xcode 12.0 or later.

What is the xcodes app?

This repository is the command line tool, while the graphical version is Xcodes.app in a separate repository, which the README points to if that is what you are after. The tool itself also moved into the XcodesOrg organisation, and the reasoning is written up in nextstep.md.

Do I have Xcode installed on my Mac?

Run xcodes installed to list the versions present on the machine, and xcodes list to see everything available to install. xcodes select changes the selected version, xcodes uninstall removes a specific one, and xcodes update refreshes the available list.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. XcodesOrg/xcodes on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/xcodesorg-xcodes.svg)](https://hysenlabs.com/projects/xcodesorg-xcodes)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/xcodesorg-xcodes.svg)](https://hysenlabs.com/projects/xcodesorg-xcodes)

Was this useful?