---
title: "強烈推薦將 REA 加入 Claude Code 或 Codex。這個名稱代表 𝗥𝗲𝘃"
url: "https://reamcp.dev/zh-tw/cases/highly-recommend-adding-rea-to-claude-code-or-codex-the-name-1fdeec"
source: "https://x.com/i/status/2109297975013081587"
source_type: "resource"
author: "Vox"
author_handle: "Voxyz_ai"
stars: 0
category: "工具與整合"
categories: ["tools-integrations"]
tags: ["agent-integration", "claude-code", "codex", "mcp", "reverse-engineering", "tutorial"]
added: "2026-10-13T04:18:02.371Z"
updated: "2026-10-13T04:18:02.372Z"
locale: "zh-tw"
content_locale: "zh-tw"
---

# 強烈推薦將 REA 加入 Claude Code 或 Codex。這個名稱代表 𝗥𝗲𝘃

強烈推薦將 REA 加入 Claude Code 或 Codex。這個名稱代表 𝗥𝗲𝘃𝗲𝗿𝘀𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝗔𝗻𝘆𝘁𝗵𝗶𝗻𝗴。在另一個應用程式中看到你喜歡的功能？讓你的智慧代理把它拆解，看看它是如何建構的，然後在你的專案中建構你自己的版本。它已經連續兩天在 GitHub 每日趨勢中排名第一，並且超過 60K 星。

## Description

你電腦上的應用程式是成品。想像一個烤好的蛋糕：你可以品嚐它，但你看不到食譜。REA 將用於拆解軟體的工具交給你的智慧代理。它一層一層地工作，向你展示每個發現的來源，然後引導你完成食譜。你可以將它指向桌面應用程式、網站和 Android 應用程式。

問它這樣的問題：
→ 「這個筆記應用程式如何在我開始輸入時立即顯示搜尋結果？」
→ 「為什麼從 Notion 複製的文字在貼到其他地方時保持其格式？」
→ 「這個老遊戲如何計算出那圈子彈？」
→ 「我們公司 10 年前的內部工具多年前遺失了原始碼。它實際上在做什麼？」

你可以隨意拆解你自己的軟體和開源程式碼。對於其他人的，先檢查條款，因為許多禁止逆向工程。不要帶來破解或繞過許可證的任務；模型很可能會拒絕。

在終端機中執行 npx rea-agents setup，當它詢問時選擇你的智慧代理，然後重新啟動它。然後發送這個提示給 Opus 5.5 👇

「我想使用 REA 來弄清楚某個軟體中的某個功能是如何工作的。
1. 首先問我想要研究哪個應用程式和哪個功能，然後讓我說明它是我自己的、開源的，還是條款允許逆向工程的軟體。如果我說不出來，就不要開始。
2. 首先弄清楚它是什麼類型的程式。如果你需要 Hopper、Ghidra 或 IDA，告訴我缺少哪一個以及在哪裡取得。不要自己安裝。
3. 用證據支持每一個發現：哪個檔案、哪個函式或位址。將你看到的與你猜測的分開。最後，用 10 歲孩子能聽懂的話解釋一切。
4. 一旦清楚了，告訴我需要編寫的最小部分，以便在我自己的專案中建構類似的東西，而不複製它的程式碼。先給我看計畫，只有在我同意後才開始編寫。」

https://t.co/K2ZekYitTW

## Original README

Highly recommend adding REA to Claude Code or Codex. The name stands for 𝗥𝗲𝘃𝗲𝗿𝘀𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝗔𝗻𝘆𝘁𝗵𝗶𝗻𝗴. See a feature you like in another app? Have your agent take it apart to see how it's built, then 𝗯𝘂𝗶𝗹𝗱 𝘆𝗼𝘂𝗿 𝗼𝘄𝗻 𝘃𝗲𝗿𝘀𝗶𝗼𝗻 in your project. It's been #1 on GitHub's daily trending two days running and is past 60K stars.

The apps on your computer are finished products. Think of a baked cake: you can taste it, but you can't see the recipe. REA hands your agent the tools made for taking software apart. It works down layer by layer, shows you where each finding comes from, and then walks you through the recipe. You can point it at desktop apps, websites and Android apps.

Ask it things like:
→ "How does this notes app show search results the moment I start typing?"
→ "Why does text copied from Notion keep its formatting when I paste it somewhere else?"
→ "How does this old game work out that ring of bullets?"
→ "Our company's 10-year-old internal tool lost its source code years ago. What is it actually doing?"

Take apart your own software and open-source code as much as you like. For anyone else's, check the terms first, since many forbid reverse engineering. Don't bring it cracking or license-bypass jobs; the model will most likely refuse anyway.

Run npx rea-agents setup in your terminal, pick your agent when it asks, and restart it. Then send this prompt to Opus 5.5 👇

"I want to use REA to figure out how a feature in some software works.
1. First ask me which app and which feature I want to study, then have me say whether it's my own, open source, or software whose terms allow reverse engineering. If I can't say, don't start.
2. Work out what kind of program it is first. If you need Hopper, Ghidra or IDA, tell me which one is missing and where to get it. Don't install it yourself.
3. Back every finding with evidence: which file, which function or address. Keep what you saw separate from what you're guessing. At the end, explain it all in words a 10-year-old could follow.
4. Once it's clear, tell me the minimum pieces I'd need to write to build something similar in my own project, without copying its code. Show me the plan first, and only start writing after I agree."

https://github.com/morluto/rea