Unfucked

What it does

Unfucked is a local filesystem version control daemon that automatically snapshots every text file on save. Rather than requiring manual commits, it continuously records file changes and stores them in a local SQLite database with content-addressed storage. Users can rewind any file to any point in time, view diffs across time windows, and restore previous versions via command-line tools.

The tool watches specified directories using system file-event monitoring (FSEvents on macOS, inotify on Linux). It respects .gitignore rules by default, skips binary files, and uses a smart debounce mechanism to batch rapid writes while keeping overhead under 1% CPU and 100MB RAM.

Who it is for

The stated motivation targets developers using AI agents or automation tools that might overwrite uncommitted work. The use cases presented also include developers who close editors without committing, accidentally delete branches, or discover mistakes in files that have been saved over. Anyone working with frequently-changing files in active development may find continuous snapshotting useful as a safety net beyond what Git provides for uncommitted work.

Pricing

The site does not show prices.

How it stands out

Unfucked differs from Git by requiring no manual commits—changes are recorded automatically on every save. Unlike operating-system-level backup tools like macOS Time Machine, it runs continuously rather than on schedules and is purpose-built for rapid development workflows. The tool uses BLAKE3 content hashing and stores identical files once, minimizing storage overhead. It is open source under MIT and Apache 2.0 licenses and installable via Homebrew or direct download.

What a founder should check

A rival builder should investigate whether developers actually adopt continuous auto-snapshotting or if the friction of manual commits remains acceptable. Second, assess whether Git users perceive real switching costs—many developers already layer stashing, branching, or IDE undo features into their workflows, and Unfucked would need to displace these habits. Third, examine the moat: as this tool gains adoption, Git could integrate similar continuous-save functionality into its ecosystem, potentially commoditizing the feature.