OmniPTY builds tmux-style splits, a file tree and a prompt into one Rust terminal

A new terminal emulator called OmniPTY appeared on the Hacker News front page on October 18 via a Show HN post linking to its GitHub repository. The project, written entirely in Rust and running natively on macOS and Linux, makes a consolidation argument: instead of pairing a plain terminal with tmux for splits, a separate file manager, a prompt framework and a copy-mode plugin, OmniPTY treats all of those as first-class features of a single application.

What ships in the box

According to the project's GitHub page, panes sit beside a file tree driven with vim-style navigation that automatically re-roots itself to the directory of whichever shell is focused. Tabs and splits group into named workspaces that can be pinned so they reopen with the same layout and directories. Copy mode converts scrollback into a vim-like buffer complete with motions, search, visual selection and yanking, and other built-ins include live scrollback search with regex toggles, jumping between previous prompts, and a history view that searches every command run in any pane along with its directory and exit status.

A shell integration that reads OSC 133 markers gives OmniPTY awareness of what is running, how long it took and whether it failed — surfaced as elapsed time in the status bar, activity dots on tabs, a flash on failed background panes and desktop notifications for long or errored commands. The status bar also renders the current workspace, tab, working directory and git branch natively, and shows when the foreground process is an ssh session, with configured hosts able to carry an accent colour on the pane border. An optional powerline prompt is compiled from TOML segments and injected without touching dotfiles; disabling it leaves starship or powerlevel10k setups untouched. Inline images work through the kitty graphics protocol, iTerm2's protocol and sixel, and pictures in the scrollback scroll, reflow and clear like text.

Under the hood

Rendering runs on the GPU via GPUI, the UI framework behind the Zed editor, while emulation comes from alacritty_terminal — Alacritty's PTY handling and VT parser — so programs like vim, htop and even tmux itself behave normally, the README says. Configuration lives in a single TOML file that reloads on save. The project states the app needs no account, includes no AI features and gathers no telemetry; the only network activity is checking whether a newer release exists.

Availability

On macOS, OmniPTY installs through a Homebrew cask or a DMG, with builds Developer ID signed and notarized. Installed copies update themselves, checking on launch and every six hours, and an update is only applied when its signature matches the key the app was built with. On Linux, builds target Wayland or X11 on x86_64 and can be installed from a PKGBUILD in the repository — an AUR package is planned once AUR registration reopens — or from a tarball whose install script works without root into ~/.local. The stated requirements are macOS 12 or later on Apple Silicon or Intel, or Linux with glibc 2.35 or newer, a Vulkan driver and libnotify for notifications. A Nerd Font build of JetBrains Mono is bundled, and the built-in prompt targets zsh and bash while other shells run fine with their own prompts.

A rename from Oxide

The project was previously known as Oxide, a name it dropped at version 0.9.0 because an unrelated company of the same name was getting in the way. The in-app updater carries existing installs across while preserving configuration, themes and pinned workspaces, and old config and cache directories are copied to new locations on first launch. Homebrew users must switch to the new cask, the $OXIDE_SESSION and $OXIDE_VERSION environment variables remain exported through the 0.9.x line before their OMNIPTY equivalents take over, and a Dock icon pinned to the old app path needs re-adding.

Why it matters

Many terminal workflows have quietly become stacks: a multiplexer, a prompt framework, a fuzzy finder and a file manager, each with its own configuration and failure modes. OmniPTY is a bet that one native, GPU-rendered application — written in Rust and reusing proven components from Zed and Alacritty — can replace that stack with tighter integration, such as a file tree that follows the shell's cd or a copy mode shared across every pane. Its explicit no-account, no-AI, no-telemetry stance also positions it against the recent wave of cloud-connected, AI-assisted terminals. Sustaining that against established rivals like Alacritty, Kitty, WezTerm and Ghostty is the hard part, but the Hacker News visibility hands the project an early and technically engaged audience.