wtf is vibe-fork?

vibe-fork is a tool for AI-assisted code translation. When you want to rewrite a working codebase from one programming language to another, like porting a C program to Rust, or a Python library to Go, this tool sits on top of Claude Code and enforces enough discipline that the translated version actually behaves the same as the original, not just looks similar. The core problem it solves is "vibe translation": an AI reads the source once, writes target code that compiles, but silently mishandles edge cases like how numbers overflow or how errors propagate. The tool fixes this with a strict four-agent loop. One agent writes the code, a second agent acts as an adversarial critic hunting for subtle differences from the original, a third applies minimal fixes, and a fourth manages design docs. Before any code is written, background hooks check that the AI has actually read the source file and the design plan. If it hasn't, the write is blocked. You'd use this if you're porting something substantial where correctness matters. The README cites two real projects built with it: translating PyTorch's C++ internals into a Rust ML framework, and translating Linux kernel C code into Rust. If you're starting something new with no existing code to port from, this tool explicitly isn't for you. What's notable is the mechanical rigor. There are no stubs allowed, no todo() markers or placeholder functions that compile but do nothing. The route table maps every target file back to its upstream source, so nothing gets written in a vacuum. Verification is always a failing test that pins a specific divergence, not a paragraph of prose claiming things match. The whole setup is language-agnostic, so the same harness works regardless of what you're translating from or to.