Authorization notice. Decomp WTF is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Who it is forA developer learning decompilation who wants to try writing matching C by hand before letting agents run.
The problemIt is hard to know whether a hand-written C function really compiles to the original bytes without a checker.
The outcomeA function whose C either matches byte for byte or shows an instruction diff explaining what differs.
What you need first
- A game you own, as a ROM, disc image or program file (the README says to use it only on games you own)
- Linux, or Windows with WSL 2 (Windows support is marked unstable); macOS is not supported
- An AI agent such as Claude Code, Codex, Antigravity CLI or opencode, or an API key for another model
- A terminal and basic familiarity with C and MIPS or PowerPC assembly
Steps
- Install Decomp WTF with
curl -fsSL https://decomp.wtf/install.sh | bashon Linux, then open the app. - Import a game you own, such as the bundled Demo Quest 64 ROM for a first try.
- Open a function in the editor and write C for it.
- Press Ctrl+Enter to compile and read the judge's instruction diff.
- Adjust the C until the function scores 100 and is marked matched.
Prompt for your agent
Using the decomp.wtf repo (i12bp8/decomp.wtf), open the bundled Demo Quest 64 ROM and write C for one function of your choice in the editor. Report the score the judge gives and the instruction diff, if any. Verify that the function only counts as matched when the score is 100 and the bytes are identical.
Caveat. The app ships with Demo Quest 64, a ROM built from public-domain code and zlib, which is the safest first target before you use a game you own.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page