gitlogue replays commits as typing animation, and warns you it is not a screensaver
A cinematic Git commit replay tool for the terminal, turning your Git history into a living, animated story.
At a glance
- What is it?
- gitlogue is a Rust terminal tool that plays your Git history back as a typing animation with tree-sitter highlighting, a staged diff view and endless random playback. The front page is unusually direct about two things: it is a visual toy, and leaving it running on an OLED panel risks burn-in.
- Who is it for?
- gitlogue earns a place on a desk where somebody wants their commit history on screen: the install is one command on four package managers, playback has pause and step controls, and the diff view is the one part with everyday use beyond decoration. It is a poor fit as an actual screensaver, since it does no power management and no blanking, and the project's own warning about OLED burn-in makes long unattended runs a hardware question rather than a preference.
- Can I use it commercially?
- Yes. ISC is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 4 days ago.
- What is it written in?
- Mainly Rust, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- unhappychoice/gitlogue5,272 ★ · +304
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| unhappychoice/gitlogue | 5k | 5.3k |
304 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Six install routes, and the piped script is the recommended one
The quickest route is a shell script piped straight into bash:
curl -fsSL https://raw.githubusercontent.com/unhappychoice/gitlogue/main/install.sh | bashThat line is the one the front page marks as recommended, and it is also the one that fetches and executes a script from a branch in one step, so you are trusting whatever is on `main` at that moment. The package manager routes are quieter: `brew install gitlogue` for macOS, `cargo install gitlogue` if you already have a Rust toolchain, and `pacman -S gitlogue` on Arch Linux. Nix has two forms, `nix run github:unhappychoice/gitlogue` to execute without installing and `nix profile install github:unhappychoice/gitlogue` to add it to your profile. Building from source takes three commands and a clone:
git clone https://github.com/unhappychoice/gitlogue.git
cd gitlogue
cargo install --path .At the top level of the repository, `install.sh`, `flake.nix`, `flake.lock` and a `Formula/` directory sit side by side, which is what you would expect from a project shipping six install paths at once.
No arguments means endless random playback
Running `gitlogue` with no arguments starts the cinematic screensaver, which is endless random commit playback. The rest of the surface is about narrowing what plays and how it ends:
# Start the cinematic screensaver
gitlogue
# View a specific commit
gitlogue --commit abc123
# Replay a range of commits
gitlogue --commit HEAD~5..HEAD
# Replay commits in chronological order (oldest first)
gitlogue --order asc
# Loop a specific commit continuously
gitlogue --commit abc123 --loop
# Watch the repository and replay new commits as they are made
gitlogue --watchA range is written with the usual two-dot revision syntax, so `HEAD~5..HEAD` and `HEAD~10..HEAD` are both accepted forms. `--watch` is the one to think about before you run it: it stays in the foreground and replays commits as they are made, which means it holds a terminal for as long as you leave it there.
The warning block says this is not a screensaver
Two warnings sit directly under the list of use cases, and they are the most useful paragraphs on the page. The first says gitlogue does not include traditional screensaver functions such as power management or screen blanking, and that it is purely a visual display tool. So the name is aspirational: nothing here dims a display or stops a GPU from drawing. The second warns about OLED burn-in, naming the culprit as static elements such as the editor background and border lines, which over extended periods may leave marks on an OLED panel. LCD displays are called generally safe from that issue. Practically, that rules out the overnight background monitor on a laptop you own, and it is why the use case list includes a screensaver for a workspace rather than a display left running all night.
Stepping goes two levels deep, from line to change
Playback is controlled from the keyboard, and the interesting part is that stepping comes in two granularities. Here is the whole table:
| Key | Action | |-----|--------| | `Space` | Toggle play / pause | | `h` | Step one line backward | | `l` | Step one line forward | | `H` (Shift+h) | Step one change backward | | `L` (Shift+l) | Step one change forward | | `p` | Previous commit | | `n` | Next commit | | `Esc` | Open menu | | `q` / `Ctrl+c` | Quit |
The menu is a smaller set, and it does not follow the same letters:
| Key | Action | |-----|--------| | `j` / `↓` | Move selection down | | `k` / `↑` | Move selection up | | `Enter` | Select item | | `Esc` | Close menu |
So `h` and `l` walk a line at a time while `H` and `L` jump a whole change, and the selection keys switch to `j` and `k` once the menu is open. Two different conventions in one program, which is worth knowing before you conclude a key is broken.
gitlogue diff shows the working tree, staged by default
The one feature with a job to do during the working day is the diff view. `gitlogue diff` visualizes staged changes, which is what you want immediately before a commit, and `gitlogue diff --unstaged` switches to the changes you have not staged yet:
# View staged changes (default)
gitlogue diff
# View unstaged changes instead
gitlogue diff --unstagedStaged is the default, so the common mistake is running the bare command while still editing and concluding that your work is missing. The quick start list also mentions filtering commits by author, and the usage guide in `docs/usage.md` covers the options.
Vendored libgit2 and thirty tree-sitter grammars in the manifest
The Cargo manifest explains the shape of the program better than any feature list. It is edition 2021, version 0.12.2, licensed ISC, and its description reads `A Git history screensaver - watch your code rewrite itself`. The dependency list is where the real cost shows. `git2` is pulled in at 0.21 with the `vendored-openssl` and `vendored-libgit2` features switched on, so the build compiles its own copies rather than using whatever your system provides. `ratatui` 0.30 and `crossterm` 0.29 supply the terminal interface, `clap` 4.6 handles arguments, `chrono` and `chrono-english` handle dates, `toml` and `toml_edit` handle configuration, and `ctrlc` with the `termination` feature covers interrupt handling. Above `tree-sitter` 0.25 sits one grammar crate per language, which is most of the manifest by line count. The `exclude` list keeps images, video, `docs/`, `examples/`, `.github/`, `Formula/`, `about.toml`, `about.hbs` and `install.sh` out of the published crate.
Settings live in one TOML file, with nine themes to start
Configuration is a single file at `~/.config/gitlogue/config.toml`, holding the default theme, the typing speed and background preferences. Nine themes ship built in, and the front page claims full customization on top of them, with the details in `docs/configuration.md` and `docs/themes.md`. The rest of the documentation is a short index: an installation guide for more options and troubleshooting, a usage guide, contributing guidelines, and an architecture overview, all under `docs/`. The repository layout backs that up: a `CHANGELOG.md` next to a `generate_changelog.sh`, a `Cargo.lock`, `codecov.yml`, a `scripts/` directory, `tests/`, and an `examples/` directory holding `test_highlighter.rs`. The Related Projects section points at GitType and at five other terminal screensavers, tarts, cbonsai, asciiquarium, cmatrix and pipes.sh, so the author is explicit that this sits in a category with alternatives.
Editorial conclusion
gitlogue earns a place on a desk where somebody wants their commit history on screen: the install is one command on four package managers, playback has pause and step controls, and the diff view is the one part with everyday use beyond decoration. It is a poor fit as an actual screensaver, since it does no power management and no blanking, and the project's own warning about OLED burn-in makes long unattended runs a hardware question rather than a preference. Before you install it, read the warning block, check that your terminal handles what you want highlighted, and look at `gitlogue diff` first, since that is the part you may still be using a month later. The cadence is fast, with the last push on 2026-11-02 and v0.12.2 released on 2026-10-31, so pin the version you try.
Frequently asked questions
How can I view my git logs with gitlogue?
gitlogue plays commits from your history as an animation. Run `gitlogue` with no arguments for endless random playback, `gitlogue --commit abc123` for one commit, `gitlogue --commit HEAD~5..HEAD` for a range, `gitlogue --order asc` to play oldest first, or `gitlogue --watch` to replay new commits as they are made. `gitlogue diff` shows staged changes, and `gitlogue diff --unstaged` shows the rest.
How do I install gitlogue on macOS, Linux or Arch?
Six routes are given. The install script runs `curl -fsSL https://raw.githubusercontent.com/unhappychoice/gitlogue/main/install.sh | bash`, Homebrew uses `brew install gitlogue`, Cargo uses `cargo install gitlogue`, Arch uses `pacman -S gitlogue`, Nix users can run `nix run github:unhappychoice/gitlogue` or install it with `nix profile install github:unhappychoice/gitlogue`, and building from source is a clone followed by `cargo install --path .`.
Does gitlogue blank the screen or manage power like a screensaver?
No. The project states that gitlogue does not include traditional screensaver functions such as power management or screen blanking, and is purely a visual display tool. It also warns that static elements such as the editor background and border lines may cause burn-in on OLED displays over extended periods, while LCD displays are generally safe.
Which languages does gitlogue highlight?
Highlighting uses tree-sitter across 32 languages: Astro, Bash, C, C#, C++, Clojure, CSS, Dart, Elixir, Erlang, Go, Godot (GDScript, Shader and Resource), Haskell, HTML, Java, JavaScript, JSON, Kotlin, Lua, Markdown, Nix, PHP, Python, Ruby, Rust, Scala, Svelte, Swift, TypeScript, XML, YAML and Zig.
How do I change the theme and typing speed in gitlogue?
Settings go in `~/.config/gitlogue/config.toml`, where you can set the default theme, typing speed and background preferences. Nine themes are built in, and the configuration and theme guides under `docs/` cover the customization options.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/unhappychoice-gitlogue)Star history chart for your README
[](https://hysenlabs.com/projects/unhappychoice-gitlogue)Was this useful?