Why Developers Look for WezTerm Alternatives

WezTerm is an excellent terminal emulator with powerful Lua scripting and GPU rendering. But it comes with a steep configuration curve. To get a productive shell environment, you still need to separately install and configure Starship, Delta, zoxide, syntax highlighting, autosuggestions, and a Nerd Font. For developers who want a turnkey experience, this setup tax adds up.

arb was built to solve exactly this problem. It takes WezTerm’s proven core — the same GPU rendering engine, the same Lua API — and adds zero-config defaults with a complete built-in shell suite. You get the power of WezTerm without the hours of setup.

Common WezTerm Frustrations

~

Configuration Overload

WezTerm requires a Lua config file for basics like font, color scheme, and keybindings. New users spend hours reading docs before their terminal looks right.

!

Missing Shell Tools

WezTerm gives you a terminal but no shell suite. You still need to separately install Starship, Delta, zoxide, syntax highlighting, autosuggestions, and a Nerd Font.

#

Binary Bloat

WezTerm’s ~80MB binary includes X11, Wayland, and Windows backends even on macOS. You pay the disk and memory cost for platforms you never use.

%

New Machine Setup

Setting up a new Mac means recreating your WezTerm environment from scratch: Lua config, font install, shell plugins, color scheme. arb makes this a single brew command.

arb vs WezTerm: Feature Comparison

FeaturearbWezTerm
GPU-accelerated rendering
Lua scripting
Built-in Starship prompt
Built-in Delta (diffs)
Built-in z (dir jumping)
Built-in syntax highlighting
Built-in autosuggestions
Nerd Font included
Zero config required
macOS optimizedCross-platform
Binary size~40MB~80MB
Shell boot~100ms~200ms

What arb Keeps from WezTerm

What arb Adds

What arb Removes (and Why)

arb’s 40MB binary (vs WezTerm’s ~80MB) comes from deliberate removal of features that macOS users do not need:

The space saved is reallocated to the built-in shell suite (Starship, Delta, z, syntax highlighting, autosuggestions) that ships with every arb install.

How to Switch from WezTerm to arb

Migrating from WezTerm to arb takes under 5 minutes:

  1. Install arb — Run brew tap szj2ys/arb && brew install arb. This installs the arb binary and GUI app.
  2. Copy your config (optional) — If you have a WezTerm Lua config, copy it: cp ~/.wezterm.lua ~/.config/arb/arb.lua. Most configs work as-is.
  3. Remove font/theme config — arb ships JetBrains Mono and Arb Dark by default. You can delete your font and color_scheme settings unless you have a custom preference.
  4. Remove shell plugin configs — If your .zshrc has lines for Starship, Delta, zoxide, zsh-syntax-highlighting, or zsh-autosuggestions, you can remove them. arb handles all of these automatically.
  5. Launch arb — Open arb. Your shell is ready with Starship prompt, Delta diffs, z navigation, and syntax highlighting. No further setup needed.

Config Translation Examples

Here is what changes (and what does not) when moving your WezTerm config to arb:

Who Should Switch from WezTerm to arb

If you spend more time configuring WezTerm than using it, arb is for you. If you set up a new machine and want a fully-equipped terminal in one brew install command, arb is for you. If you are a macOS developer who wants the power of WezTerm with the convenience of a turnkey solution, arb is for you.

If you rely on WezTerm’s cross-platform support (Linux, Windows) or need specific advanced features like SSH domains, you may want to stay with WezTerm.

Frequently Asked Questions

Yes. arb started as a WezTerm fork and retains WezTerm’s Lua scripting API and GPU-accelerated rendering. It adds a built-in shell suite, zero-config defaults, and macOS-specific optimizations to create a turnkey terminal experience.
Most WezTerm Lua configs work with arb with minimal changes. arb uses the same wezterm Lua module and API. The config file lives at ~/.config/arb/arb.lua. Font and color scheme settings can usually be removed since arb provides polished defaults.
Currently arb is macOS-only. It is optimized for macOS with Metal rendering and native integration. If you need cross-platform support, WezTerm remains an excellent choice.
arb maintains its own development pace and may diverge from WezTerm over time. The Lua scripting API remains compatible for core use cases. arb focuses on macOS-specific improvements and built-in tooling rather than tracking every WezTerm upstream change.
Open an issue on GitHub Issues. arb is MIT-licensed and actively maintained. You can also run arb doctor to diagnose common configuration issues before reporting.