Hunk Open source

What it does

Hunk is a terminal-based, review-first diff viewer purpose-built for looking at code changes produced by AI coding agents, rather than plain unified diff text. It renders a multi-file review stream with sidebar navigation, split/unified/auto layouts, and syntax highlighting, so a session where an agent touched a dozen files is easier to step through than scrolling raw terminal output.

What is inside

• Inline annotations next to code showing AI/agent-authored context
• Watch mode that auto-reloads as an agent keeps editing
• Keyboard, mouse, pager, and Git difftool interaction modes
• Auto-detection of Jujutsu and Sapling alongside Git, using native revsets
• A TypeScript extension system (~/.config/hunk/extensions/) and a skill file system for live-session agent integration

Works with

Git (including as a configured pager/difftool), Jujutsu, and Sapling; designed to sit alongside any terminal coding agent whose diffs you want to review, rather than being tied to one specific agent vendor.

How to install or connect

curl -fsSL https://hunk.dev/install.sh | sh
npm i -g hunkdiff
brew install hunk
mise use -g hunk

Runs as a standalone binary on macOS, Linux, and Windows; the npm path requires Node.js 22+. It can also be wired in as your default git diff pager or git difftool for a drop-in upgrade to your existing review habits.

Maintenance and safety

Actively maintained (876 commits, 9.3k stars, 305 forks, MIT licensed) with a community Discord. It's a local, offline diff viewer with no network calls required for its core function; no safety concerns surfaced in the documentation, and it doesn't need write access to your repository beyond what your normal Git/Jujutsu/Sapling tooling already has.

Who should use it

Developers running one or more terminal coding agents who want a faster, more structured way to review the resulting multi-file diffs than scrolling through raw git diff output — especially useful when agents touch many files per task, and want to see agent-authored context inline rather than in a separate summary.