Whetuu: Zero-config cross-shell prompt written in Zig.

What it does

Whetuu is a shell prompt and command history tool written in Zig. It provides a single status line that works across fish, bash, and zsh shells. The prompt displays git branch information, language logos, and execution time. Whetuu also replaces the up-arrow key with its own history picker that prioritizes commands run in the current directory, with a keyboard shortcut to view all history. Failed commands are not stored in history.

Who it is for

The tool targets developers using macOS or Linux who want a consistent, opinionated prompt experience without configuration. It supports users across the three major interactive shells. The zero-configuration approach appeals to developers who prefer sensible defaults over customization.

Pricing

The site does not show prices.

How it stands out

Whetuu emphasizes simplicity and speed. It is distributed as a single compiled binary with no configuration files, themes, or tuning options. The prompt renders in approximately two milliseconds. Installation is a one-command process on supported platforms, and the tool can upgrade itself without external dependencies like curl, tar, or shell scripts. The history picker integrates directory-aware search while preventing typos from cluttering the history feed. The project is open source and written in Zig rather than more common systems languages.

What a founder should check

A competitor should verify the market appetite for zero-config prompts against the demand for customization. Most successful prompt tools like Starship and Oh My Zsh thrive on extensive theming and plugin ecosystems—the opposite of Whetuu's philosophy. A founder should examine whether Whetuu's speed advantage (two milliseconds versus typical multi-millisecond renders) creates meaningful user value or remains imperceptible in practice.

Second, assess distribution and switching costs. Whetuu relies on users manually installing a binary and editing shell config files. Established prompts distribute through package managers and shell frameworks with one-command setup. Check whether the current install experience creates friction compared to alternatives.

Third, evaluate the sustainability of the opinionated approach. If users discover they want any customization—custom colors, additional modules, or different layouts—they cannot achieve it. Understanding whether the target audience truly rejects customization or simply hasn't found the right tool yet determines the long-term market size.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.