TRANSCRIPTEnglish

DeepSeek + REA Is INSANE

6m 58s1,105 words166 segmentsEnglish

What this video covers

This guide demonstrates how pairing DeepSeek harness with the open-source REA (Reverse Engineer Anything) tool enables users to inspect software codebases, extract underlying architecture patterns, and rebuild customized business applications. The presenter explores three practical examples, including an agent control deck, a task-splitting lead reactor, and a complete website redesign. Key takeaways highlight best practices for generating evidence reports, scoping analysis to first-party code, and providing detailed design prompts.

Key takeaways

  • REA (Reverse Engineer Anything) is an open-source tool that allows AI agents to inspect native apps, web apps, desktop apps, and websites directly on a local machine.
  • DeepSeek harness seamlessly integrates REA via terminal commands, utilizing models like DeepSeek V4.1 Flash via direct access or OpenRouter.
  • REA documents transparent findings in an evidence file, stating verifiable proof and noting code or bundles it could not read.
  • Case Build 1 recreated the multi-agent architecture of Ion UI into a multi-agent dashboard for a dental practice.
  • Case Build 2 uncovered hidden backend logic within the Agent app to construct an automated lead-processing workflow.
  • Case Build 3 demonstrated live browser mapping of a personal website to rebuild it with refined aesthetics and layout.
  • Key best practices include generating evidence markdown files, focusing searches on primary app code rather than vendor libraries, and respecting software licensing.

Topics covered

Overview and Technical Setup
Explains the capabilities of the REA tool and how to configure it inside DeepSeek harness using Node 24, including running diagnostic health checks and routing through OpenRouter if API quotas are met.
Application Rebuild Case Studies
Details three hands-on builds: reverse engineering Ion UI to build a 6-agent practice management deck, discovering backend routing in Agent to create a lead flow reactor, and analyzing a live website to rebuild a modern front-end.
Key Lessons and Best Practices
Outlines essential strategies for AI reverse engineering, such as insisting on evidence logs, narrowing file scope to exclude bloated third-party dependencies, adhering to ethical/legal guidelines, and defining explicit design styling.
“It launched a real browser, loaded juliangoldie.com, and captured the page structure, the fonts, the scripts, and where every button leads.”
▶ 5:32 · HEAR IT IN THE VIDEO

FULL TRANSCRIPT

0:00

DeepSeek can now look inside apps and

0:02

rebuild them. I plugged a tool called

0:05

REA, short for [music] reverse engineer

0:07

anything, into DeepSeek harness. Then I

0:10

pointed it at three apps on my [music]

0:12

Mac. It opened each one up, showed me

0:15

the evidence of how it works, and

0:17

rebuilt the idea as a beautiful business

0:19

tool, an agent control deck, a lead flow

0:22

reactor, and my own website rebuilt

0:25

[music] from scratch. I'll show you

0:27

every build, every prompt, and the exact

0:30

setup step by step.

0:32

So what is REA? It's an open source tool

0:35

on GitHub from Morluto. It has over

0:38

438,000

0:40

stars and it's MIT licensed. It gives

0:43

your AI agent one set of tools for

0:45

reverse engineering, native programs,

0:48

JavaScript and Electron desktop apps,

0:50

.NET apps, Android apps, and websites.

0:54

Everything runs on your own machine. And

0:56

the part I love, every answer comes with

0:58

the evidence behind it plus what it

1:01

could not prove.

1:02

Now the brain. DeepSeek harness is

1:05

DeepSeek's own agent app. It's open

1:07

source too, MIT licensed with over

1:09

275,000

1:12

stars. Everything inside it is a plugin,

1:14

so REA just slots in. I'm running

1:17

DeepSeek V4.1 Flash. It's fast and it

1:21

can look at screenshots which matters

1:23

when it checks its own work. Here's the

1:25

setup. Open your terminal and run npx

1:28

REA-agents setup -- client dsh. That

1:33

registers REA inside DeepSeek harness

1:36

and installs the reverse engineering

1:37

skill. One thing caught me out. REA

1:40

needs node 24. If setup stops and asks

1:43

for node, install node 24 next to your

1:46

current one and run it again. Then run

1:49

npx rea agents doctor. You want the

1:52

DeepSeek harness line marked healthy.

1:54

Restart harness, open a new session,

1:57

pick your folder, and pick your model.

1:59

One more

2:00

If DeepSeek tells you your account quota

2:02

is used up, go to settings, then models,

2:05

add OpenRouter with your key and pick

2:07

DeepSeek v4.1 Flash from that list.

2:11

That's exactly what I did for these

2:12

builds. That's it. Three commands and

2:15

DeepSeek can now look inside software.

2:18

Quick one. If you want my best setups

2:20

for DeepSeek and REA, like the three

2:22

prompts from this video, the evidence

2:24

checklist, and the design brief that

2:26

made these builds look this good,

2:28

they're all inside the AI Profit

2:30

Boardroom. You also get the faceless

2:32

video skill I used to make this video,

2:34

plus a community of people building with

2:36

AI every day, and a new tutorial almost

2:39

every day. The link is in the comments

2:41

and the description, or go to

2:43

aiprofitboardroom.com.

2:45

Build one. The agent control deck. Ion

2:49

UI is an open-source desktop app that

2:51

runs several AI agents side by side. I

2:54

asked DeepSeek to use REA to find out

2:57

how it does that, then build my own

2:59

version for a dental practice. Here's my

3:01

prompt. Use REA to reverse engineer how

3:05

Ion UI runs several AI agents side by

3:08

side. Write the evidence to evidence.md.

3:11

Then build my own version, an elegant

3:14

agent control deck with six live agents,

3:17

light trails, and a command box. Watch

3:19

what happens. It loads the reverse

3:21

engineering skill, unpacks the app, and

3:24

maps it. 38,000 pieces inside one app

3:27

file. 548 source files checked. Then it

3:32

hit a limit. Two bundles were too big to

3:34

pass, so it raised its own memory limit,

3:37

narrowed the search to the app's own

3:39

code, and kept going. And here's the

3:41

honest part. Its report says exactly

3:43

which conclusions came from the code and

3:46

which parts it could not read. It found

3:48

the agent manager at the heart of the

3:50

app, one adapter for each kind of agent,

3:52

and how each conversation tracks its

3:54

status. Then it built this. Six live

3:58

agents for Bright Smile Dental. Lead

4:00

finder, inbox, SEO writer, booking,

4:03

support and reports. Each card streams

4:06

what it's doing. Light trails flow from

4:08

the DeepSeek lead to every agent. And

4:11

when I type a new task, it flies to the

4:13

right agent, and that agent picks it up.

4:16

Build two, the lead flow reactor. Agent

4:19

is another open source app. You give it

4:21

a job, and it splits that job across a

4:24

team of worker agents. I asked DeepSeek

4:26

how the splitting works. My prompt, use

4:29

REA to find out how Agent breaks a

4:32

request into tasks and hands them to

4:34

worker agents. Write the evidence. Then

4:37

build a lead flow reactor for my dental

4:39

practice. This is where REA earned its

4:42

place. The desktop app turned out to be

4:44

just the front. The real task splitting

4:46

lives in a Python backend shipped inside

4:49

the app. DeepSeek would never have

4:51

guessed that. REA found it. So it

4:54

rebuilt that pattern for leads. New

4:56

leads fly into the reactor. Each one

4:59

gets split into tasks, qualify, reply,

5:03

book, and follow up. The tasks shoot out

5:06

to four worker lanes. And when an

5:08

appointment gets booked, the whole

5:09

screen celebrates. I can add a lead by

5:12

hand, and it goes straight through the

5:14

same flow. Build three, my own website

5:17

rebuilt. My prompt, use REA's website

5:21

analysis on juliangoldie.com,

5:23

which I own. Map the sections, fonts,

5:26

scripts, and buttons. Then rebuild it as

5:29

an elegant premium version. This time,

5:32

REA did something different. It launched

5:34

a real browser, loaded juliangoldie.com,

5:37

and captured the page structure, the

5:39

fonts, the scripts, and where every

5:41

button leads. 15 sections mapped. Then

5:45

DeepSeek rebuilt it with my real

5:47

sections and words. Big serif headlines

5:50

that fade in as you scroll. Soft, warm

5:52

light. Every service, every result, and

5:55

real reviews laid out cleanly. The first

5:58

version copied a banner I didn't want.

6:00

So I asked for a revision right in in

6:02

same chat, and it fixed it in one pass.

6:05

Here's what I learned from these three

6:07

builds. One, always ask for an evidence

6:10

file. It keeps deep seek honest, and you

6:12

can check every claim. Two, on big apps,

6:15

tell it to focus on the app's own code,

6:18

not the bundled libraries. Three, only

6:20

look inside software you own or open

6:23

source software you're allowed to study.

6:25

Then build your own version with your

6:27

own name and design. Four, ask for the

6:30

look in detail, colors, fonts, motion.

6:33

That's the difference between a plain

6:35

dashboard and something people actually

6:37

want to use. If you want the exact

6:39

prompts for all three builds, the setup

6:41

checklist, and the design brief, they're

6:43

inside the AI Profit Boardroom along

6:46

with [clears throat] the faceless video

6:47

skill that made this video. The link is

6:49

in the comments and the description, or

6:51

go to aiprofitboardroom.com.

6:53

Thanks for watching, and I'll see you in

6:55

the next one.

GET MORE FROM YOUR TRANSCRIPTS

Sign up for free and unlock interactive viewer, AI summaries, translations, concept maps, and more. No credit card required.