Forge TUI / Practical guide
A terminal file manager and Git workflow, together.
Forge is a keyboard-first terminal user interface built in Rust. It combines a file manager, source preview, and Git operations in one workspace. This guide explains what it does, when it is useful, and how to try it.
What is Forge TUI?
Forge is a terminal file manager and Git TUI. Its Files view shows a directory tree with status cues and previews for text, code and Markdown. Its Git view shows changes, staged files and history alongside diffs. It also supports branch operations, stash and remote synchronization.
Forge is for developers who work in a local terminal, SSH session or tmux and want to move from locating a file to reviewing its changes without switching to a separate application. It is not a replacement for the Git command-line interface or a full IDE.
How to browse files, review diffs and commit
1. Install and open a repository
For Linux x86_64/aarch64 (glibc) and macOS Intel/Apple Silicon, download a prebuilt release or inspect and run the installer. The installer verifies the downloaded archive using SHA-256 checksums.
curl -fsSL https://creature-studio.github.io/forge/install.sh | sh
cd /path/to/your/project
forge2. Explore the files
Use F1 for Files and F2 for Git, or click the workspace tabs. Use Ctrl-P to find a filename, Ctrl-F to search contents, and F3 to switch Markdown between rendered preview and source. The built-in editor is available, but you can still use your usual editor.
3. Review and stage Git changes
The Git view separates working changes from staged changes. Inspect side-by-side or full-file diffs; stage or unstage a file with s or u while focused on the Git list. You can also stage individual hunks or lines from the diff view. Unstage does not discard the working file.
4. Commit or sync
Open the commit editor with c in the Git view. Review what is staged before committing. When the Git sidebar is focused, p and P handle pull and push. Destructive discard and delete operations require confirmation.
How is Forge different from lazygit or terminal file managers?
These tools emphasize different parts of terminal work. Lazygit concentrates on Git interaction. File managers such as ranger, lf and nnn concentrate on navigating files. Forge's design combines a file tree, file/code preview and Git changes in one window. These categories overlap, and the right choice depends on how you work; Forge does not claim to replace every feature of those tools.
The main difference is context continuity: find a file, read its current contents, inspect its Git diff, stage an intended change and commit — all without rebuilding context in a different interface.
Common questions
Does Forge require a graphical desktop?
No. Forge is a terminal application. It is suitable for ordinary terminals and can be used in environments such as SSH or tmux, subject to terminal capabilities. It supports keyboard and mouse navigation.
Is Forge available on Windows?
The official v0.2.0 prebuilt release matrix contains Linux glibc and macOS binaries, not a native Windows build. Windows users can use WSL with a compatible Linux environment or build from source.
Does Forge replace my editor or Git?
No. Forge includes a lightweight text editor and can launch an external editor, while its Git write operations use the Git CLI. It is intended to complement rather than replace a full editor or familiar Git commands.
Will Forge change files automatically?
Browsing and previewing are read-oriented. Stage and unstage are explicit actions; unstage retains your working-directory edits. Destructive delete and discard operations ask for confirmation. Review the diff before applying Git changes.
How does Forge handle updates and fonts?
Run forge update --check to inspect the latest release or forge update to upgrade. Forge includes Unicode icons by default, so a Nerd Font is optional; ASCII icons are also supported.
Is it free and open source?
Yes. The repository includes the MIT license, and the source code and release history are available on GitHub.
Where to find the source, documentation and downloads
For feature details and code-level verification, consult the project's own resources rather than relying on a third-party summary:
- GitHub repository and current README
- Latest released binaries and checksums
- Full usage reference
- Release and update details
- English product homepage with real terminal screenshots
Not all features in the development branch are necessarily part of the latest release. Use the release tag and its source tree to verify what your installed version includes.