Getting jcode running takes less than a minute on most systems. This page walks you through the fastest way to install it, then points you to a full guide for your specific platform.
Quick Install (Fastest Path)
If you just want jcode running right now, pick your platform below.
macOS and Linux
curl fsSL https://jcode.sh/install | bash
Windows 11 (PowerShell 5.1 or newer)
irm https://jcode.sh/install.ps1 | iex
Once the command finishes, open a new terminal window and run:
jcode
If the interface opens, jcode is installed and ready. From here you can log in to an AI provider such as Claude, OpenAI, or Gemini and start your first session.
For most people, that’s all it takes. But installation steps differ slightly by platform, especially around package managers, architecture, and permissions, so use the guides below for full detail on your system.
Install jcode on Windows 11
Jcode supports Windows x86_64, including native installs and WSL2.
The Windows installer checks your processor architecture automatically and verifies the downloaded file against the release’s SHA256SUMS before installing anything.
Extras like Alacritty and the optional global launch hotkey are not installed by default and require your explicit consent during setup.
If a release does not include a matching Windows build, the installer stops rather than attempting a long compile in the background.
In that case, a source build is available using the BuildFromSource flag, which requires Git, Rust, and Visual Studio 2022 Build Tools with the Desktop development with C++ workload.
Full Windows setup, including Defender and SmartScreen notes, is covered in the dedicated Windows install guide.
Install jcode on macOS
Jcode runs on both Apple Silicon and Intel Macs. There are two supported ways to install it. Using the install script:
curl fsSL https://jcode.sh/install | bash
Using Homebrew:
brew tap 1jehuang/jcode
brew install jcode
Homebrew is a good option if you already manage other command line tools that way, since it handles updates through the same workflow. The full macOS guide covers both methods in detail, along with what to do if either one runs into permission issues.
Install jcode on Linux and Termux
Jcode fully supports Linux on x86_64 and aarch64. The standard install script works on most distributions:
curl fsSL https://jcode.sh/install | bash
Termux on Android is also supported, but it needs two extra packages before running the installer, since Termux uses its own C library instead of the standard Linux one:
pkg install glibc patchelf
curl fsSL https://jcode.sh/install | bash
These packages let the installer adjust the downloaded binary so it works correctly inside Termux’s environment. The full Linux and Termux guide explains why this step is needed and covers troubleshooting for both aarch64 and x86_64 devices.
Build jcode from Source
If you want full control over your build, or your platform does not have a prebuilt release available, jcode can be compiled from source on any supported platform:
git clone https://github.com/1jehuang/jcode.git
cd jcode
cargo build release
For people doing repeated local builds or working on jcode’s own codebase, there is a faster path for Linux x86_64:
scripts/dev_cargo.sh build release p jcode bin jcode
scripts/dev_cargo.sh print setup
This script automatically uses sccache when it’s available and prefers a fast local linker setup with clang and lld instead of assuming a mold configuration will work on every machine.
Running it with print setup shows you exactly which linker and cache setup is active, which is useful if a build is running slower than expected. After building, symlink the binary to your PATH with:
scripts/install_release.sh
The full source build guide covers each of these steps individually, along with what to check if a build fails partway through.
Uninstall, Reinstall, and Fix a Broken Install
Jcode includes an uninstall script with two levels of removal. A standard uninstall removes the installed binaries and launcher, but keeps your config, auth, and sessions in place, so a fresh reinstall picks up right where you left off:
curl fsSL https://raw.githubusercontent.com/1jehuang/jcode/master/scripts/uninstall.sh | bash s yes
A full wipe removes everything, including config, auth, sessions, logs, and memory. This is the option to use if your install is broken and a normal reinstall isn’t fixing it:
curl fsSL https://raw.githubusercontent.com/1jehuang/jcode/master/scripts/uninstall.sh | bash s purge yes
You can add dry run to either command to preview exactly what would be removed without deleting anything, which is a good way to check before running the full wipe version.
The dedicated uninstall and reinstall guide walks through both options step by step and covers common signs that point to a broken install worth fixing this way.