Eleven: a visual REA workbench for agents

Eleven is an open-source, agent-first reverse-engineering visual IDE / workbench. It puts code views, AI chat, and change review in one desktop window. It is not a new decompiler engine: analysis still rides engines such as Ghidra, Rizin, and jadx (via the REA stack and Eleven’s own setup). Product site: eleven.chizi.app. Repo: Zfinix/eleven. REA toolbox: morluto/rea. Chinese twin: /zh/blog/eleven-rea-workbench/.

On rea.run the teaching pin for the MCP/CLI layer remains [email protected] (/blog/rea-agents-6-5-0/). If you are new to REA itself, start with /blog/rea-beginner-guide/ and the install demo /docs/install-demo/, then come back here for the GUI workbench path.

Snapshot (re-verified 2026-10-16)

Stars move. Re-fetch before you quote. Stars ≠ doctor-green on your box and ≠ permission to analyze arbitrary store binaries (/blog/evaluating-rea-claims/).

What Eleven is (and is not)

REA CLI/MCP vs Eleven GUI

Operators often ask: “Do I need Eleven if I already run REA?” Use both when the job needs eyes on decompiled text and a human-in-the-loop accept/skip loop; use CLI/MCP alone when you already have a strong agent host and Evidence-first scripts.

Install / demo for REA on this site: /docs/install-demo/ · lab: /lab/ · beginner guide: /blog/rea-beginner-guide/.

Supported formats

From the product “What it opens” / FAQ pages (2026-10-16 fetch):

Four views of every native function (site copy): pseudocode, assembly, control-flow graph, hex — from Ghidra or Rizin.

Engines: Ghidra / Rizin / jadx

REA on the CLI still treats Hopper / Ghidra / IDA as bring-your-own for many workflows (/faq/setup-vs-providers/). Eleven’s product FAQ states it can download Java+Ghidra for its own first-run path — that is Eleven’s packaging, not a claim that rea-agents ships those engines.

Platforms and install (v0.1.8)

Release notes: v0.1.8. Prefer reading the release body before upgrading teaching labs.

Agent surface (ACP)

Site lists agents that speak the Agent Client Protocol, including Claude, Codex, Gemini, Cursor, OpenCode, Aster, plus “any ACP agent.” Eleven runs locally; whatever the agent reads still follows that model vendor’s data policy — same as using the agent elsewhere.

Operator checklist: first authorized session

• [ ] Confirm the target is own / authorized / clean-room (/compliance/, /faq/legal-boundary/).
• [ ] Install Eleven v0.1.8 for your OS from eleven.chizi.app (or the curl/irm one-liners above).
• [ ] Sign in to an ACP agent you already pay for / host; Eleven does not replace that subscription.
• [ ] Wait for background Java/Ghidra setup if you need deep pseudocode; or use Rizin / jadx paths for speed.
• [ ] Open a disposable copy of the binary/APK — never your only production artifact.
• [ ] Ask the agent to explain one function; require Evidence-style specifics (address, name, callers) not vibes.
• [ ] If patching: verify output landed in Downloads as a new file; keep the original untouched.
• [ ] Optionally keep REA CLI pinned: npx -y [email protected] doctor --json for MCP hosts outside Eleven (/blog/rea-beginner-guide/).
• [ ] For guided interactive practice on this site (separate from Eleven): /lab/ · showcase /showcase/dx-ball/.

# REA teaching pin on rea.run (CLI/MCP hosts — complementary to Eleven GUI)
npx -y [email protected] doctor --json

# Eleven Mac install one-liner (from product site)
curl -fsSL https://eleven.chizi.app/install.sh | bash

How this fits the rea.run teaching path

1. Learn REA vocabulary + Evidence habit: /blog/rea-beginner-guide/.
2. Pin and understand 6.5.0: /blog/rea-agents-6-5-0/.
3. Walk install UI: /docs/install-demo/.
4. Practice in /lab/ on fixtures you may analyze.
5. Use Eleven when you want a desktop workbench that keeps the agent next to decompiled text — still on authorized targets only.

Compliance

• Authorized teaching / own software / written rights / clean-room fixtures only. No crack, keygen, or DRM-bypass how-tos (/compliance/, /faq/legal-boundary/).
• Byte patches in Eleven go to a copy (Downloads), not the original — keep that discipline in labs.
• Engines (Ghidra, Hopper, IDA, jadx, …) remain subject to their own licenses; BYO where required.
• rea.run is a community operator guide; footer disclaimer stays low-key. Not affiliated with Zfinix/Eleven authors or morluto beyond documenting public repos.
• Media under /media/blog/eleven-rea-workbench/ are product-demo stills and a short demo clip hosted for this article.

Sources

• Product: eleven.chizi.app (fetched 2026-10-16: v0.1.8, platforms, formats, engines, Android 61 MB / 73,471 methods)
• GitHub: Zfinix/eleven (API snapshot 2026-10-16: 503★, 78 forks, Apache-2.0)
• Release: v0.1.8
• REA: morluto/rea · pin /blog/rea-agents-6-5-0/
• On-site: /blog/rea-beginner-guide/ · /docs/install-demo/ · /lab/ · /showcase/dx-ball/ · /zh/blog/eleven-rea-workbench/

FAQ