Unfucked (unf)
Filesystem flight recorder in Developer tools
Snapshots every file save, including agent edits, so changes between commits can be recovered. Critics object that it is a closed-source daemon they cannot inspect.
Snapshots every file save, including agent edits, so changes between commits can be recovered. Critics object that it is a closed-source daemon they cannot inspect.
23 people gave an opinion
- recommend it
- 16
- criticize it
- 7
- approval share
- 70%
Recommended in 2 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: not recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: not recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 16 people recommend itNeeds 10 or more, met.
- 2.3 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 2 of 13 monthsNeeds 4 or more, not met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Safety net for changes between commits
“Your tool probably has a more tailored UX to handling these inter-commit changes though so there could still provide complementary value there.”
Comment from 27 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” “does solve a real issue I've certainly had quite a few times already where this would have been very useful”
Comment from 1 Mar 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” “This will be a nice safety net.”
Comment from 27 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” Records file writes from any agent
“works with any agent and any file in the folder whether it's edited by the agent or anyone by tracking all file writes”
Comment from 28 Feb 2026 on Hacker News “this is the problem I'm solving for. Agents use tools and may be in multiple places editing”
Comment from 27 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” Useful with easy setup
“this seems insanely useful and well thought out”
Comment from 26 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” “One install, one init, and then it just works.”
Comment from 28 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save”
What people warn about
Each mark is one comment
Closed-source daemon with filesystem access
“I am not installing a closed-source daemon with access to the filesystem from an unknown (to me) developer.”
Comment from 27 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” “I'm not brew installing a closed source daemon.”
Comment from 28 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” “closed source daemon with access to all files is a 100% non-starter”
Comment from 27 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” - Comment from 27 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save”
- Comment from 28 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save”
Cannot trust or read the code
“A downloadable tarball is a lot better than nothing, but it still makes more work to evaluate a random project”
Comment from 28 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” “Just can't trust it unless it's transparent.”
Comment from 27 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” “I'm not going to rely on or trust anything this important to code I can't read.”
Comment from 27 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” Terrible name and branding
“Good project, nice presentation, absolutely terrible name and branding”
Comment from 28 Feb 2026 on Hacker News “Great idea, terrible name.”
Comment from 28 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” Another tool to babysit
“I do mind having to babysit one more (albeit super useful) tool”
Comment from 28 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save” “if I have 10 different projects across 10 different drives, then, yes, I would need to babysit it”
Comment from 28 Feb 2026 in “Show HN: Unfucked (unf) – a filesystem flight recorder that snapshots every save”
What people said
22 of the 26 comments that mention it, newest first. Each links to the original comment.
“does solve a real issue I've certainly had quite a few times already where this would have been very useful”
“if I have 10 different projects across 10 different drives, then, yes, I would need to babysit it”
“One install, one init, and then it just works.”
“Good project, nice presentation, absolutely terrible name and branding”
“This does not contain the source.”
“A downloadable tarball is a lot better than nothing, but it still makes more work to evaluate a random project”
“I do mind having to babysit one more (albeit super useful) tool”
“This tool doesn't help with that either”
“now I can't download it anymore”
“Great idea, terrible name.”
“I'm not brew installing a closed source daemon.”
“works with any agent and any file in the folder whether it's edited by the agent or anyone by tracking all file writes”
“This would be great as aVSCode(ium) extension.”
“closed source daemon with access to all files is a 100% non-starter”
“this is the problem I'm solving for. Agents use tools and may be in multiple places editing”
“I'm not going to rely on or trust anything this important to code I can't read.”
“Just can't trust it unless it's transparent.”
“Your tool probably has a more tailored UX to handling these inter-commit changes though so there could still provide complementary value there.”
“I am not installing a closed-source daemon with access to the filesystem from an unknown (to me) developer.”
“No open source code means no use.”
“This will be a nice safety net.”
“this seems insanely useful and well thought out”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.