Authorization notice. Eleven is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.
Reverse engineering. Comparing builds of software you do not own may conflict with its license, so use builds you are authorized to analyze.
Who it is forA security reviewer or release engineer who needs to see what changed between two builds of the same program.
The problemComparing two binaries byte by byte shows little, so it is hard to tell which behavior actually changed.
The outcomeA function-level list of changes between the two builds that you can read like a code review, with an agent summary of what matters.
What you need first
- A supported OS: macOS 14 or later on Apple Silicon, Windows x64, or Linux x64
- An ACP-compatible agent (Eleven installs ACP adapters when they are needed)
- Rizin for fast opening, or Ghidra 12.x with Java 21 for the clearest pseudocode
- jadx if you plan to open Android APK files
- A binary, APK, GPU kernel, shader or model file you have the right to analyze
Steps
- Open the first build in Eleven and create a project for it.
- Open the second build in Eleven as a separate project or in the same project, following the diffing workflow in the app.
- Run the diff view to see the functions that changed.
- Ask your agent to summarize the most important changes and the functions they affect.
- Save the project with ⌘S if you want to share the comparison as a
.elevenfile.
Prompt for your agent
Using the Zfinix/eleven app, diff the builds at <path-to-old-build> and <path-to-new-build>, then ask the agent to list the five most important changed functions with a one-line reason each. Verify that each function name exists in both builds.
Caveat. The README describes diffing by function but does not give the exact menu steps, so check the app for how to start a diff.
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