any Android app on your phone is now an open book for Claude Code the stack: Claude Code → REA (MCP) → headless JADX apk → map → trace → spec → build step 1 → npx rea-agents setup step 2 → full JDK 17+ and the pinned JADX 0.7.1 jar. this is where most setups die step 3 → map the manifest, entry points and DEX before reading any method step 4 → investigate_feature walks UI → handler → the one method that does the work step 5 → SPEC.md from behavior only, build your version in a fresh session the big mistake: reading class names. R8 turns them into a.b.c. anchor on strings, resource ids, framework calls the limit: logic hidden in native .so files or packers won't come back as clean Java. and it's static only, no running or patching save this before you pick your first APK
你手機上的任何 Android 應用程式現在對 Claude Code 來說都是一本打開的書,技術堆疊:Cla
一則 X 貼文,描述 Claude Code → REA (MCP) → headless JADX 工作流程:用於對應 Android APK、追蹤某項功能、根據觀察到的行為撰寫 SPEC.md 並重建應用程式,包含設定步驟以及關於 R8 混淆和原生函式庫的注意事項。
關於這個案例
你手機上的任何 Android 應用程式現在對 Claude Code 來說都是一本打開的書
技術堆疊:Claude Code → REA (MCP) → headless JADX
apk → 對應 → 追蹤 → 規格 → 建置
步驟 1 → npx rea-agents setup 步驟 2 → 完整 JDK 17+ 和固定版本的 JADX 0.7.1 jar。大多數設定死在這裡 步驟 3 → 在讀取任何方法之前,先對應 manifest、進入點和 DEX 步驟 4 → investigate_feature 沿著 UI → handler → 真正完成工作的那個方法 步驟 5 → 僅根據行為撰寫 SPEC.md,在全新工作階段中建置你的版本
最大的錯誤:讀取類別名稱。R8 會把它們變成 a.b.c。錨定字串、資源 id、框架呼叫
限制:隱藏在原生 .so 檔案或加殼器中的邏輯不會以乾淨的 Java 回來。而且它僅限靜態,不能執行或修補
在挑選第一個 APK 之前儲存這個
安裝設定
安裝方式請查看原始來源。
原文 / README
any Android app on your phone is now an open book for Claude Code
the stack: Claude Code → REA (MCP) → headless JADX
apk → map → trace → spec → build
step 1 → npx rea-agents setup step 2 → full JDK 17+ and the pinned JADX 0.7.1 jar. this is where most setups die step 3 → map the manifest, entry points and DEX before reading any method step 4 → investigate_feature walks UI → handler → the one method that does the work step 5 → SPEC.md from behavior only, build your version in a fresh session
the big mistake: reading class names. R8 turns them into a.b.c. anchor on strings, resource ids, framework calls
the limit: logic hidden in native .so files or packers won't come back as clean Java. and it's static only, no running or patching
save this before you pick your first APK


