CLI tool
sachaos/viddy avatar
sachaos/viddy

viddy and the time machine it bolts onto watch

👀 A modern watch command. Time machine and pager etc.

5,451 stars101 forksRustMIT

At a glance

What is it?
Viddy is a Rust rewrite of the watch command that keeps the periodic execution and coloured diff, then adds a time machine you can rewind, a pager, vim keymaps and saved history. The install paths are broad, the configuration file is optional, and the release line has moved three times since late 2024.
Who is it for?
Viddy fits someone who runs the same command in a loop all day and wants the history kept rather than scrolled away, and who is comfortable with a key driven terminal interface. It does not fit a script that needs unattended, non-interactive watching, since the pager and the time machine are both interactive.
Can I use it commercially?
Yes. MIT 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 98 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 21, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • sachaos/viddy5,451 ★ · +31
Star history
Repository2026-09-232026-11-21
sachaos/viddy5.4k5.5k

31 Stars in the last 59 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Time machine mode turns a loop into a rewindable tape

The feature that is not in watch is the time machine mode, entered with SPACE. Output accumulates as a timeline you can scrub, the way you would scrub a video, rather than a buffer you scroll and lose.

The keys are split into small steps and large steps. Shift-J goes to the past and Shift-K back to the future. Shift-F and Shift-B jump further in each direction, Shift-O goes to the oldest position held, and Shift-N returns to the current position. That is six bindings for one idea, and the difference between the plain and the extended pair is how far the timeline moves.

Because the mode is interactive and bound to a TUI, it changes what kind of tool this is. Watching a build that takes ten seconds and then paging through the last forty runs by hand is a different activity from leaving watch in a second terminal pane and never touching it.

Look back history is stored, not scrolled

The second feature that survives a closed terminal is look back history: history is saved and can be loaded again. The dependency list explains the mechanism. `rusqlite 0.32.1` is pulled in with the `bundled` feature, which compiles SQLite into the binary, so there is no external database to install and no service to keep alive.

The README does not document a retention setting, a pruning command, or where the file lands by default.

Colour handling follows the same pattern of doing the work in-process. `ansi-parser 0.9.1` and `ansi-to-tui 4.1.0` are both in the dependency list, which is how a watched command that prints ANSI escapes still renders inside the interface, and `strip-ansi-escapes 0.2.0` is there for the paths where it should not.

The pager half of the keymap is borrowed from less

Output can be viewed in a pager, and the bindings for it follow a convention you already have in your fingers: j for the next line, k for the previous one, h and l to move left and right, Control-F to page down, Control-B to page up, g for the top of the page and Shift-G for the bottom.

The rest of the table is single-letter toggles. SPACE enters the time machine, s toggles suspend, b toggles the ring terminal bell, d toggles the diff, t toggles the header or title display, ? opens the help view, and / opens text search. Suspend is the practical one: you can stop execution without leaving, and restart it when you are ready.

Every one of those bindings can be reassigned. The config file maps logical names to physical keys; in the example the time machine actions use arrow keys and Ctrl combinations, while scroll_left, scroll_right, scroll_up and scroll_down stay on h, l, k and j.

Six package managers, and the Linux tarball is one release behind

There are more install routes than most command line tools of this size. Cargo and Homebrew are the two the project publishes itself:

shell
cargo install viddy
brew install viddy

Then the community-maintained list: APT packages from pkg.haus for Debian stable, testing and unstable on amd64 and arm64, built from source at release tags and installed with `sudo apt install viddy`; MacPorts with `sudo port install viddy`; Scoop on Windows, which needs git first because adding a bucket depends on it; the Arch Linux AUR with `yay -S viddy`; Alpine with `apk add viddy` once the community repository is enabled; and asdf with a plugin, an install and a global setting. Anything else comes from the release page.

The manual Linux path is the one with a wrinkle. The wget line in the README downloads the v1.3.0 tarball and moves the binary into /usr/local/bin, while the crate manifest is at version 1.3.1. Copy that line as written and you install the previous release.

shell
wget -O viddy.tar.gz https://github.com/sachaos/viddy/releases/download/v1.3.0/viddy-v1.3.0-linux-x86_64.tar.gz && tar xvf viddy.tar.gz && mv viddy /usr/local/bin

viddy.toml is optional, and its keys are mostly names

Viddy works with no configuration file at all. If you want different keybindings or different defaults, the file goes at `$XDG_CONFIG_HOME/viddy.toml`, or on macOS at `~/Library/Application Support/viddy.toml`, which is the one path in this project that is not obvious.

The general block decides how your command is invoked and what gets drawn:

toml
[general]
no_shell = false
shell = "zsh"
shell_options = ""
skip_empty_diffs = false
disable_mouse = true

`no_shell` sits next to `shell` and an empty `shell_options`, which is where the shell wrapper is configured. `skip_empty_diffs` and `disable_mouse` are the two display switches. The file gives you the key names and defaults, not a sentence each, so the names are doing the explaining.

The keymap block then rebinds individual actions by logical name, and the time machine defaults are arrows and Ctrl combinations:

toml
[keymap]
timemachine_go_to_past = "Down"
timemachine_go_to_future = "Up"
timemachine_go_to_now = "Ctrl-Shift-Up"
scroll_left = "h"
scroll_right = "l"
scroll_up = "k"
scroll_down = "j"

One more support path is not in that file at all. Shell alias support is documented through a comment on issue 2 rather than as a config key.

The dependency list describes a terminal UI with a database

Cargo.toml is worth reading before you judge what this binary does, because the dependency list is the architecture. `ratatui 0.26.3` and `crossterm 0.27.0` are the drawing and input layers, `tui-input 0.9.0` and `tui-widget-list 0.9.0` are also listed, and `tokio` with the full feature set carries the async runtime.

Diffing is delegated rather than reinvented, through `dissimilar 1.0.9` and `similar 2.6.0`. Configuration comes from the `config` crate plus `toml 0.8.19`, with `json5 0.4.1` and `serde_json` also present. Crashes are handled deliberately: `better-panic`, `human-panic` and `color-eyre` are all in there, so a panic gives you a readable message instead of a stack trace and a prompt.

Argument parsing is clap 4.5.21 with the derive feature, and version strings come from `vergen 8.3.2` at build time, which is what a `build.rs` in the repository is for. The Makefile stays deliberately small: `cargo test` for tests, `cargo fmt` for formatting, `cargo clippy` for lint, and a help target that greps itself.

Three tags since 2024, and the last push was 2026-08-16

The release history is short and spaced out. v1.2.1 shipped on 2024-11-16, v1.3.0 on 2024-11-28 twelve days later, and v1.3.1 on 2026-06-14. The last push to the repository was on 2026-08-16. The project is not archived, and work continued after that tag, but the gaps are measured in months rather than days, so treat any expectation of a steady release train as wrong.

The crate is edition 2021, MIT licensed, authored by Takumasa Sakao. The repository carries a rust-toolchain.toml, which pins the compiler the project builds against rather than whatever version your distribution happens to ship.

One naming note. Viddy is Nadsat, the fictional gang argot from A Clockwork Orange, where the word means to see. As for the logo, the gopher marks are under a Creative Commons 3.0 attribution licence, with the original Go gopher credited to Renee French.

Editorial conclusion

Viddy fits someone who runs the same command in a loop all day and wants the history kept rather than scrolled away, and who is comfortable with a key driven terminal interface. It does not fit a script that needs unattended, non-interactive watching, since the pager and the time machine are both interactive. Before switching from watch, check three things: the interval behaviour against your original flags, which shell your command runs under if you set shell in viddy.toml, and whether the version you install matches the one your distribution packages.

Frequently asked questions

What does viddy mean?

It is a Nadsat word meaning to see. Nadsat is the fictional argot used by the gangs in the novel and film A Clockwork Orange, and the project took the name from it.

What is viddy, the command line tool?

It is a Rust watch command that executes your command periodically and displays the result, with colour output and diff highlight, plus a time machine mode, saved history, a pager, search, and vim style keymaps. It installs with cargo, Homebrew, APT, MacPorts, Scoop, the AUR, Alpine's apk, or asdf.

What does 'viddy well' mean in the project's greeting?

It is a line at the top of the README, addressed to the Go gopher that appears in the logo. It plays on the Nadsat word for seeing, so it reads as a parody greeting rather than a command or an option.

How does viddy compare to the original watch command?

It keeps watch's basic behaviour, running the command periodically and showing coloured output with a diff highlight, then adds time machine mode, saved and loadable history, a pager, text search, suspend and restart, vim style keymaps and configurable bindings and colours.

Is viddy a real word or a made up name?

It comes from Nadsat, the invented slang of A Clockwork Orange, rather than from ordinary English. The README also says the gopher logo is licensed under Creative Commons 3.0 Attributions, and that the original Go gopher was designed by Renee French.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. sachaos/viddy on GitHub
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/sachaos-viddy.svg)](https://hysenlabs.com/projects/sachaos-viddy)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/sachaos-viddy.svg)](https://hysenlabs.com/projects/sachaos-viddy)

Was this useful?