rgx: debug regexes inside your terminal

If regex101 already covers every regular expression you write, rgx is probably unnecessary. The project's own README says the tool is strongest for developers doing regex-heavy work in terminal-centric workflows, and that is the right bar for today's pick. 1

rgx is a Rust terminal UI for testing and debugging regular expressions. It has step-through execution, three regex engines, code generation, live stream filtering, and a newly surfaced ReDoS analysis path for spotting catastrophic backtracking. 2

The fastest path depends on your package manager. The README lists six install routes, including Cargo, Homebrew, AUR, a shell installer, GitHub Releases binaries, and source builds. 1

# Cargo
cargo install rgx-cli

# Homebrew
brew install brevity1swos/tap/rgx

# AUR
yay -S rgx-cli

ReDoS analysis is optional. If you want rgx to analyze catastrophic backtracking patterns, install with the redos feature enabled. 1

cargo install rgx-cli --features redos

The core workflow is simple: open a regex, test it against input, then step through the match process instead of guessing why a capture group behaved differently than expected. rgx supports the default Rust regex engine, fancy-regex for features such as lookaround and backreferences, and PCRE2 for patterns that need recursion, conditionals, or possessive quantifiers. 1

The shortcuts are built for terminal work rather than browser tabs. Ctrl+D starts the step-through debugger, Ctrl+A runs ReDoS analysis when the feature is installed, Ctrl+G generates code, Ctrl+U exports to regex101, and Ctrl+X opens the grex integration. 1

The recent hook is ReDoS. On 2026-06-19, the project added optional ReDoS analysis through the rxray crate, and on 2026-06-24 the README headline was updated to include "ReDoS analysis" alongside step-through execution, three engines, code generation, and live stream filtering. 3 2

Say you are reviewing a log parser before it goes into a service that sees untrusted input. The pattern works on your sample lines, but one nested quantifier looks suspicious. In a browser tool, you can confirm matches. In rgx, you can keep the test inside the terminal, switch engines, step through the capture behavior, then run ReDoS analysis before the regex lands in a production path. 1

rgx

A more practical flow is to keep a failing input file beside the code and iterate there:

rgx ./fixtures/problem-lines.txt

That makes rgx a fit for engineers who already debug text processing in Vim, tmux, shell scripts, CI logs, or ripgrep output. It is less compelling if your regex work is occasional and copy-paste-driven.

The current repo snapshot is modest: 220 stars, 4 forks, 1 watcher, Rust as the main language, and MIT OR Apache-2.0 licensing. 1 The star count was unchanged from the June 25 snapshot in this scan, so rgx is today's pick because it is practical and newly updated, not because it is spiking. 1

The latest release is v0.14.1, published on 2026-06-08, with prebuilt binaries for Linux, macOS, and Windows targets. 4 crates.io lists 1,241 total downloads and 39 published versions for rgx-cli. 5

The weak part is community proof. Hacker News has two rgx submissions, both posted by the author, with 2 points and 3 points respectively and no outside user discussion. 6 7 Reddit has one r/commandline thread with 16 points, 76% upvotes, and 10 comments; visible comments include a positive "It's good! Tried it" and a separate complaint asking whether the post and votes looked bot-like after users hit 404 links. 8

Two maintenance signals also deserve attention. The changelog says, "Until chosen, rgx is in de-facto maintenance mode," after a note about the developer reinvesting in SaaS projects. 9 Recent commits still happened, but the commit history since 2026-06-06 shows claude as co-author on the recent changes. 3 The AUR package is also behind upstream at v0.12.1-1, with 0 votes and 0 popularity. 10

Adopt if your job already involves regex-heavy terminal work and you want step debugging, engine switching, code generation, and ReDoS checks in one local TUI.

Try if you occasionally debug complex production patterns. The install path is short, and one real failing regex will tell you more than a demo.

Skip if regex101 is already enough, if you need strong community validation before adding a tool, or if maintenance-mode language is a blocker for your team.