wezterm's release tags stop in February 2024 while the branch keeps moving, and the README is one link
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
At a glance
- What is it?
- wezterm is a GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust, with the client, the GUI, and the multiplexer server split into separate workspace crates. What the repository does not give you is an install command, a version scheme, or a support commitment: installation is a single documentation link, the newest release tag is a 2024 build stamp, and the author describes it as a spare time project.
- Who is it for?
- wezterm fits someone who wants a terminal with a multiplexer and a scriptable configuration, is willing to read the documentation site rather than a README, and accepts that support comes from one person in their spare time.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly Rust, 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.
Star history
- wezterm/wezterm29,564 ★ · +514
| Repository | 2026-09-28 | 2026-11-15 |
|---|---|---|
| wezterm/wezterm | 29.1k | 29.6k |
514 Stars in the last 48 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The installation section is one link, and the release list ends in February 2024
The Installation heading in the README contains no command, no package name, and no version. It contains a URL to https://wezterm.org/installation and nothing else. The release list is where the version story gets strange. The three most recent releases are named 20240203-110809-5046fc22, 20240128-202157-1e552d76, and 20240127-113634-bbcac864, published on 2024-02-03, 2024-01-29, and 2024-01-27, so nothing on that list is newer than early 2024. The last push to main is dated 2026-10-26, and the repository is not archived, so the code is current while the tags are old. The consequence is that the tags in this repository do not tell you what to install. Which build you get is decided on the website, and pinning to a tag here means pinning to a 2024 build.
Release names are date-time-hash stamps, so there is no version to compare
Read a release name as three fields rather than a version. In 20240203-110809-5046fc22, the first field is the date, the second is the time of day, and the third is a short commit hash. That is a build stamp, not a semantic version, and the two earlier names follow the same pattern on consecutive days. The difference matters the moment you want to answer a question an operator would ask, which is what changed between the build I have and the one you are proposing. With stamps, there is no ordering guarantee, no minor line to reason about, and no intermediate names to diff. Every comparison has to be made against the commit history instead.
Four macOS framework crates are pinned with = so upstream bumps break the build
The workspace dependency list pins the Apple framework bindings to exact versions: cocoa at =0.25.0, core-foundation at =0.10.0, core-graphics at =0.24.0, and core-text at =21.0.0. The equals sign is the whole point, since it tells Cargo not to accept a compatible bump. cairo-rs is handled differently, at 0.18 declared with default-features turned off and a comment directing you to the patch.crates-io section of the manifest. The consequence is a maintenance shape you can see in the file: an upstream release in any of those four crates is not picked up automatically, so a maintainer has to update the pin by hand. That is a reasonable way to keep a desktop build reproducible, and it is also a recurring piece of work that the project has to keep doing.
Formatting wants a nightly toolchain and the test target wants cargo-nextest
The Makefile is short and it tells you what contributing costs. Formatting is not plain cargo fmt:
fmt:
cargo +nightly fmtTests are not plain cargo test either:
test:
cargo nextest run
cargo nextest run -p wezterm-escape-parser # no_std by defaultSo a contributor needs a nightly Rust toolchain and cargo-nextest, and neither is vendored in the repository. The second line explains itself: the escape parser is a no_std crate, so it is run as a separate invocation. The check target runs cargo check on the workspace and then on four named packages, and the build target fires four separate builds, for wezterm, wezterm-gui, wezterm-mux-server, and strip-ansi-escapes, threading a BUILD_OPTS variable through each. None of that is exotic, but it is all tooling you install before your first patch.
The client, the GUI, and the multiplexer server are separate workspace members
The workspace is split further than a single binary would suggest. Alongside the main wezterm package, the members list includes wezterm-gui, wezterm-mux-server, wezterm-ssh, wezterm-uds, wezterm-surface, wezterm-cell, wezterm-escape-parser, wezterm-dynamic, wezterm-blob-leases, wezterm-open-url, bidi, and strip-ansi-escapes, with two codegen directories excluded from the workspace entirely. The release profile sets opt-level to 3, and the dev profile has a commented-out split-debuginfo setting carrying the note that it is disabled because it breaks builds on Windows. The structural consequence is that the pieces can be reasoned about separately, a multiplexer server that is not the GUI, and remote or socket transport as its own crate. What the README does not do is say how those pieces are meant to be launched together.
Support is one person's spare time, and the README opens by saying so
The help section is unusually direct about capacity. It says this is a spare time project, so please bear with me, and then offers three channels: the GitHub issue tracker, GitHub Discussions, and a Matrix room via Element.io. It also says which is which, noting that the Discussions and Element rooms are better suited for questions than bug reports, while inviting you to use whichever you are comfortable with. No response time is stated anywhere. For an adopter, that shapes two decisions. First, an outage you need fixed is competing with a queue that has one maintainer, and second, picking the wrong channel costs a round trip, because a question filed as a bug and a bug filed as a question both have to be redirected. Sponsoring is described as covering the fees required to maintain the project and to validate the time spent on it.
Configuration is a Lua API split across crates, and none of it is in the README
The layout says more about the configuration surface than any prose would. There is a lua-api-crates directory, a luahelper directory, and two workspace dependencies pointing into that tree, with battery resolved from lua-api-crates/battery and color-funcs from lua-api-crates/color-funcs. So the configuration language is Lua, and the API is not one file but a set of per-area crates. None of it appears in the README, which is 198 words and points at wezterm.org for anything user facing. The user documentation is in the repository, under docs/ beside docs-internal/, and is built with MkDocs through ci/build-docs.sh, which the docs and servedocs targets run. Two other root files are aimed at other audiences: PRIVACY.md, and README-DISTRO-MAINTAINER.md, next to a .copr directory, which is how a distribution gets a build.
Editorial conclusion
wezterm fits someone who wants a terminal with a multiplexer and a scriptable configuration, is willing to read the documentation site rather than a README, and accepts that support comes from one person in their spare time. It is a poor fit if you need a version you can pin and diff, since the release names are date-time-hash stamps and the newest is from 2024, and it is a poor fit for a team without Rust bandwidth, because the build pins four macOS framework crates exactly and expects a nightly toolchain for formatting. Before you commit, read wezterm.org/installation rather than the repository, decide which channel you are installing, and check the LICENSE.md file at the root, since the README states no licensing terms.
Frequently asked questions
What is WezTerm?
It is a GPU-accelerated cross-platform terminal emulator and multiplexer, written by @wez and implemented in Rust. The user facing documentation and guide live at https://wezterm.org/, and the repository README is only a pointer to it.
Is WezTerm written in Rust?
Yes. The tagline states it is implemented in Rust, the repository's primary language is Rust, and the Cargo workspace is made up of about sixteen members, including wezterm-gui, wezterm-mux-server, wezterm-ssh, and wezterm-uds.
how to install wezterm
The README's Installation section contains no command at all, only a link to https://wezterm.org/installation. The repository does not name a package, a version, or a channel, so the install decision is made from the documentation site.
how to use wezterm multiplexer
The README does not document multiplexer commands. The structure is visible in the repository instead, with a mux directory, a wezterm-mux-server workspace member, and a wezterm-client crate, and the Makefile builds wezterm-mux-server as a target of its own.
how to install wezterm on windows
Nothing in the README is platform specific; installation is one link for every platform. The Windows-related detail in the repository is a build setting: the dev profile has split-debuginfo commented out with a note that it is disabled because it breaks builds on Windows.
Is WezTerm better than Kitty?
The README makes no comparison with any other terminal emulator. Its own claims are that WezTerm is GPU-accelerated, cross-platform, and both a terminal emulator and a multiplexer, and it points at https://wezterm.org/ for the user facing details.
Official sources
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.
[](https://hysenlabs.com/projects/wezterm-wezterm)Star history chart for your README
[](https://hysenlabs.com/projects/wezterm-wezterm)Was this useful?