Viddy CLI
The CLI repeats a selected command, highlights output changes and retains history for users and agents to compare.
- 5,443 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The tool reruns the supplied command with its normal permissions and may retain sensitive output.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/viddyDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The tool reruns the supplied command with its normal permissions and may retain sensitive output.
This is third-party code. Review the repository files before installing.
What it does
Viddy repeatedly runs a chosen command and displays its output. Change highlighting and saved history let users revisit earlier results without searching a long log. History can be saved and loaded. An agent can help choose an observation command for a test service, build or project. Viddy supports color, search and suspension. Rewinding views past output; it does not roll back program state.
Who it is for. Support engineers observing repeated command output and comparing changes over time.
Good fit when
- Diagnosis needs changes in read-command output.
- Earlier output must be revisited after several runs.
- Observation needs pausing without losing history.
- An agent has prepared a command for interactive monitoring.
Not a fit when
- Repeating the command could destroy data or repeat a payment.
- You expect output rewind to restore service state.
- There is no interactive terminal for viewing.
Example request
Choose a safe status-reading command for our test service in Viddy and explain which changes to observe.Limitations
The first installation route requires Cargo and a working Rust toolchain on the machine. Viddy really reruns the command, so choose an operation safe to repeat throughout the observation period. Saved history may contain credentials or service data; restrict access before giving files to an agent. Keyboard controls and rendering depend on the terminal, so test a short session with a harmless command first.
How to disable. Suspend execution and exit Viddy. Check the command process and saved history files separately.
FAQ
How do I pause reruns?
Press `s` to pause or resume repeated execution.
How do I inspect older output?
Space toggles time-machine history mode.
How do I show differences?
Press `d` to turn change highlighting on or off.
Can I search for text?
Yes. Press `/` and enter the text to find.
Where are keys configured?
In `viddy.toml` in the platform configuration directory.
Discussion
No questions or reviews yet.
Related
CLI toolsThe terminal pager opens long files and streams, pins headers and helps users inspect logs alongside an agent.
Named clipboards retain terminal text and files so results move between commands and sessions without a graphical file manager.
A CLI that analyzes Claude Code and Codex sessions: standup summary, productivity report and tips in the status line
A CLI and skill for Yandex Tracker and Wiki: short output readable by people and agents alike, instead of raw MCP payloads costing thousands of tokens
A Yandex 360 toolkit: Tracker, Wiki and Forms via a CLI, an MCP server, a Python SDK and a Claude Code plugin
A dashboard and JSON CLI for Claude Code, Codex, Cursor Agent and Pi sessions: who waits for approval, who works, who is idle.
README in short
Colors, keybindings and shell behavior are configurable. History navigation moves between older and current results.