A tour of real demos reverse-engineering QuickTime, TickTick, WhisperFlow, CapCut, and Loom with AI coding agents, and the ethics question none of them settle.
Posted
yesterday
Duration
Format
Reaction
educational
Views
1.1K
53 likes
57 · 43
Big Idea
The argument in one line.
A tool called REA lets AI coding agents inspect any closed-source app's binary and rebuild its features in under an hour, turning software customization into an unsettled ethical question.
Who This Is For
Read if. Skip if.
READ IF YOU ARE…
A developer curious about using AI agents to inspect and extend software you don't have the source code for.
Someone frustrated with one missing feature in an app you otherwise like and want to patch yourself.
A builder interested in using an existing app's UX as a reference while building your own original product.
Someone who runs a live app and wants a way to catch bugs that code review alone misses.
SKIP IF…
You're looking for an exact step-by-step tutorial — this is a reaction video, not a walkthrough.
You need a settled legal or ethical verdict on software reverse engineering — the video raises the question without resolving it.
TL;DR
The full version, fast.
REA (Reverse Engineer Anything) is an MCP server and skill that lets coding agents like Claude Code inspect a closed-source app's binary using tools such as Ghidra, Hopper, and IDA Pro, then rebuild its features in plain English. The video walks through real demos: rebuilding QuickTime Player with granular playback speed, cloning TickTick's task manager including a premium calendar feature hidden behind a paywall, rebuilding WhisperFlow's local voice dictation, cloning a CapCut-inspired video editor, running REA against a live app to catch a real billing bug, and recreating Loom's recording bubble. Each clone took under an hour and reached roughly 80% parity in one shot, with manual fixes needed for details like color and multi-line text input. The host keeps circling back to whether this is legitimate customization or just copying.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Cold open and stats: REA is described as the fastest-rising repo on GitHub, climbing past 330,000 stars.
01:12 – 01:39
02 · REA Setup
Installing REA is one npx command that previews changes, backs up config, and asks before touching anything critical.
01:39 – 03:27
03 · QuickTime Player Clone
A single GitHub link plus a one-line prompt rebuilds QuickTime Player with a new granular playback-speed feature in under 30 minutes.
03:27 – 04:30
04 · How REA Works
REA is a wrapper around existing tools (Ghidra, Hopper, IDA Pro) that gives an agent plain-English commands for binary reverse engineering.
04:30 – 06:54
05 · TickTick Clone
A rebuilt TickTick clone matches the original's task lists, calendar, categories, and tags almost exactly, built under ground rules that kept the original app untouched.
06:54 – 07:39
06 · Premium Features
REA reconstructed TickTick's paywalled calendar view purely from the app's compiled code, without the agent ever accessing the paid version.
07:39 – 09:54
07 · Where the Clone Fails
The clone missed a basic detail, overdue-task color, even though it copied a paywalled feature, and couldn't handle multi-line text entry the original supported.
09:54 – 13:39
08 · WhisperFlow Clone
A rebuilt WhisperFlow runs local dictation across multiple languages; the key prompt change was asking REA what could be improved, not just copied.
13:39 – 16:03
09 · Bug Testing
Pointed at a live site instead of its code, REA found a billing bug where two accounts were charged the wrong amount, tracing it to the final total-calculation step.
16:03 – 19:21
10 · CapCut-Inspired Video Editor
Scoping the first prompt narrowly produced a working editor with import, split, and auto-captions that functions like CapCut but looks nothing like it.
19:21 – 19:48
11 · Inspiration vs Copying
The host argues that once you start removing features and making your own calls on top of someone else's app, the result becomes your own software.
19:48 – 21:00
12 · Loom Clone
A Loom clone rebuilt the moveable recording bubble and window-picker behavior, storing files locally instead of in the cloud, built to dodge a pricing complaint rather than copy Loom's UI.
21:00 – 21:15
13 · Final Take
Every demo took under an hour; the host closes by asking whether this is a legitimate productivity win or a step too far.
Atomic Insights
Lines worth screenshotting.
REA (Reverse Engineer Anything) is an MCP server plus skill that wraps existing reverse-engineering tools like Ghidra, Hopper, and IDA Pro so an AI agent can use them with plain-English commands.
The repo reportedly gained 779 stars in a single day and has since climbed past 330,000 stars, which the host calls possibly the fastest-rising repo he's tracked.
Setup is one command, npx rea-agent setup, which previews the exact changes, backs up your existing config, and asks before touching anything critical.
A cloned QuickTime Player reached about 80% completion in one shot, with the remaining 20% spent on font, look-and-feel, and export format tweaks.
REA reconstructed a TickTick premium feature, the full calendar view, from the binary alone, without the agent ever having paid for or seen the premium UI.
The same clone missed small details a paywall didn't block, like matching the color used for overdue tasks, showing no clear pattern in what gets copied correctly.
Reverse-engineering a live app with REA caught a billing bug code review missed: two accounts were charged a different price than what displayed on screen, including one charged zero.
The billing bug traced back to the very last calculation step: line items, discounts, and tax were all correct, but the final total add-up was wrong.
A cloned Loom replicated the moveable recording bubble and window-picker behavior, not the visual design, and stored recordings locally instead of in Loom's cloud.
A developer on the show compared unauthorized app-cloning to copying the Mona Lisa and selling it, while the host argues that building on a UI you admire and changing it still makes it your own software.
Takeaway
What REA actually makes possible, and where it breaks
WHAT TO LEARN
An AI agent wrapped around existing reverse-engineering tools can rebuild roughly 80% of a closed-source app's features in under an hour, but what it gets right and wrong doesn't follow an obvious pattern.
01Reverse Engineer Anything
REA gives a coding agent the ability to inspect a closed-source app's binary and rebuild any feature it finds, not just read code you already have access to.
The project went from near zero to over 330,000 GitHub stars, a growth rate the host says may be the fastest of any repo he's tracked.
02REA Setup
Installing REA is a single command, npx rea-agent setup, that previews the exact changes before making them and backs up your existing agent config.
The tool pauses and asks for confirmation before touching anything it flags as critical, rather than acting fully autonomously.
03QuickTime Player Clone
Giving the agent a GitHub link plus a one-line prompt is enough; naming the target application is the only other input needed to start a clone.
A full working clone with one new feature was ready in 20-30 minutes, with about 80% of the work done in a single pass.
The remaining 20% of effort went into smaller follow-up prompts for font, visual polish, and export format support, not core functionality.
04How REA Works
REA isn't a new decompiler itself, it's a wrapper that lets an agent operate existing professional tools (Ghidra, Hopper, IDA Pro) through plain-English commands.
Those underlying tools already made this kind of reverse engineering possible, so REA's real contribution is removing the time and skill needed to use them, not a technical breakthrough.
The agent is given dozens of specific intent tools, like opening a binary or finding its strings, that map directly onto reverse-engineering workflows experts already use.
05TickTick Clone
The working prompt explicitly separated investigation from building: analyze the real app first, write findings to an evidence file with sourcing, then build a new app with a different name and new icons.
Setting firm ground rules up front, like only reading and never modifying the original app, kept the clone legally safer while still copying structure and behavior.
The clone matched the original's task lists, calendar, categories, and tagging system closely enough that side-by-side screens looked almost identical.
06Premium Features
REA reconstructed a feature hidden behind the original app's paywall purely from the compiled code, without the agent ever having access to the paid version.
This shows the technique can expose functionality a company intentionally gates, not just features that are already visible for free.
07Where the Clone Fails
A real clone that's 80% complete still misses details: this one couldn't handle multi-line text entry the original supported natively.
Small visual details, like which status used which color, were inconsistent even though they looked like the easiest things to copy correctly.
There's no obvious pattern to what gets reproduced well versus what gets missed; a paywalled feature was copied while a basic color wasn't.
08WhisperFlow Clone
The single most effective prompt addition was explicitly asking the agent to explain what could be improved in the app's files, not just replicate them as-is.
The rebuilt dictation tool ran its transcription locally instead of sending audio to the cloud, which the builder argues is both faster and safer than the pattern it copied.
Multi-language input carried over into the clone, showing the rebuild captured behavior, not just a static UI.
09Bug Testing
Pointing REA at your own live site and telling it not to read the code forces it to find bugs the way a real user would, uncovering issues invisible from a code review alone.
In this test, the agent found a billing bug where two accounts were charged a different amount than the price shown on screen, including one account charged nothing.
Tracing the bug step by step isolated the exact failure point: every line item, discount, and tax calculation was correct, and only the very last total add-up step was wrong.
The same pass also caught a separate issue where the backend accepted negative seat counts, letting an account oversell past its plan's allowed limit.
10CapCut-Inspired Video Editor
Scoping the first prompt narrowly rather than asking for every feature at once kept a sprawling app like a full video editor manageable to rebuild.
The result functioned like a video editor with import, split, and auto-caption support, but didn't visually resemble the app it was inspired by, undercutting the idea that this was a straight copy.
Core interaction patterns, like a keyboard shortcut to split a clip at the playhead, transferred over even though the surrounding UI looked completely different.
11Inspiration vs Copying
Once you start removing features and making your own design decisions on top of someone else's software, the result arguably becomes legitimately your own.
Using an existing product as a reference point gives a practical head start: you inherit decisions that already worked instead of guessing from zero.
12Loom Clone
This clone copied functionality, not visual design: the moveable recording bubble and the ability to change which window you're recording, not the original's exact UI.
Storing recordings locally instead of in a company's cloud was a deliberate design choice made possible once the underlying behavior was understood and rebuilt independently.
A real complaint about an existing product's pricing was the direct motivation for rebuilding the one feature that mattered, rather than attempting a full feature-for-feature copy.
Glossary
Terms worth knowing.
REA (Reverse Engineer Anything)
An open-source MCP server and agent skill that lets AI coding agents inspect a closed-source application's compiled binary and rebuild its features from what they find.
MCP (Model Context Protocol)
A standard that lets an AI agent call external tools, in this case giving the agent access to reverse-engineering software it couldn't otherwise run on its own.
Binary
The compiled, non-readable version of an app that actually runs on your computer, as opposed to its original human-readable source code.
Ghidra
A free reverse-engineering tool originally built and released by the NSA, used to analyze and decompile software binaries.
Hopper
A paid reverse-engineering and disassembly tool for Mac used to analyze compiled applications.
IDA Pro
The long-standing industry-standard commercial disassembler used by professional reverse engineers.
Decompiler
A tool that converts a compiled binary back into a more readable, code-like form, though not the original source code.
“Rea itself isn't a decompiler. It's nothing revolutionary or special.”
undercuts the hype in one blunt line, good contrarian hook→ TikTok hook↗ Tweet quote
03:20
“Essentially, REA has made every software into open-source software.”
crisp one-line claim that reframes the whole tool→ newsletter pull-quote↗ Tweet quote
13:06
“It's like copying the Mona Lisa and selling it or copying the Mona Lisa and using it.”
sharp analogy that frames the ethical pushback→ IG reel cold open↗ Tweet quote
15:00
“Most accounts were priced correctly, but two accounts saw one price on screen and got charged another, with one seeing half the real total and the other seeing zero.”
concrete, scary bug a dev audience will recognize→ TikTok hook↗ Tweet quote
18:55
“Once you start cutting back features and making your own decisions, isn't it your own software?”
the rhetorical question that frames the whole ethics debate→ newsletter pull-quote↗ Tweet quote
The Script
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
17px
analogy
Everyone's talking about an insane new way to copy software. I've played with it. I've used it.
I've understood it. But now I want to see some real use cases, which I'm going to show you. These are the best that I found online.
And then you tell me whether you think this will actually improve your productivity and your business in a legitimate way, or maybe it's just wrong. presented by Zapier, the AI automation company. But first, let's understand what it does.
This is the best video that I found on that.
build you a version people are doing this for games for software they're cracking desktop applications that have been closed source for the last 20 years so it's called rea which stands for reverse engineer anything and it's one of the fastest rising repos on github right now something like By the way, since this video was shot, it actually has climbed even more.
It is up to over 330 ,000 stars. I think this is growing faster than OpenClaw and just about any other fast. This might be the fastest growing repo out there.
Let's talk about how to set it up, and then I want to really get you into the use cases. Setup is super simple. It's just npx rea -agent setup.
It shows you a plan of what it's going to change. It backs up your config, adds the MCP server, and a skill that teaches your agent how to do the investigation. And then it asks before touching anything critical.
Super easy. Let's get into QuickTime Clone. Let's look at it.
All right. So what you're looking at on screen is the before and after of rebuilding something called QuickTime Player. It's been a staple app to help you replay any video, whether it's an mp3, .mov, or what have you.
Now, use this app to rewatch the final version of any YouTube video before it goes live and you see it. But it has a flaw. And the flaw is, let's say I want to vary the speed at which I'm playing it back.
I only have a few options I can pick from. Double, faster, fast, normal, or half. Now, obviously, there are other softwares out there that I can use that have this feature.
But let's say I really like the UI and the simplicity and the elegance of this app. And all I want is a carbon copy that has this additional feature. Okay.
Interesting. Fair point. I wouldn't call it a flaw that it doesn't have this speed the way that he wants it, but I understand the real legitimate use for that.
Let's look at the prompt that he used. You literally just have to send a prompt like this, which is install this and help me use it to reverse engineer an app. And then I just simply give it the GitHub link.
And even if you're using something like GLM 5 .2 in the cloud, it will install it in under a minute. And all you have to do is tell the target. And once I told it, my target was Quick Player.
Since this harness is running on a computer, it has access to all of these applications and can get to work right away. And depending on what model you're using, within 20 to 30 minutes, you'll have the first version ready to go. Shockingly simple.
Let's look at the result that he got. And just like any other app, you'll be able to right -click, click on Open With. I'll click on Tempo here.
And 80 % of this was in one shot. The only things that I added on after with a couple extra prompts was basically changing the font, the look and feel, and allowing me to export to different formats. And from the get -go, I was able to increase the speed to whatever I wanted at a much more granular level, see the audio waves, change the pitch, and do anything that I could do in QuickTime Player.
You know what? This was actually always the dream of open -source software. Somebody gives you software that works one way but allows you to change it and make it into something else.
And now, essentially, REA has made every software into open -source software. I want to look at just a quick image of how it works, and then we'll get into more use cases. Rea itself isn't a decompiler.
It's nothing. revolutionary or special. It's basically wrapping the serious tools reverse engineers already use, which is things like Ghidorah, which is free and from the NSA, Hopper on the Mac, and IDA Pro, which is the expensive industry standard.
So all of this reverse engineering was possible before with enough time and enough money. The difference now is the friction has been removed. So these tools are all incredibly powerful and also notoriously hard to learn.
What REA does is give your agent dozens of plain text. intent tools on top of them things like open this binary find the strings follow the function colors so it can find its way through and understand the code okay let's go on one more um this is one where he just legit just copies an app let's take a look at what ai for this example we're going to use tick tick which millions of people use to capture ideas organize life and do something creative It's basically a to -do list and project management app that I believe is the favorite of MKBHD, Marques Brownlee, the tech reviewer.
Okay, so here's the prompt that he used. You can see the prompt here is find TickTick on my Mac. Use RIA to figure out the whole app.
the task list, the calendar, the timeline, how everything fits together. Show me the evidence you find in the app files. Don't change anything in TickTick itself.
Then build me my own version called TaskYard with sample tasks to start. And underneath that, I gave the ground rules. Only read TickTick, never change it.
Don't copy its icons. Make new ones. Write every findings to an evidence file with where it came from and build a real Mac app that compiles and runs.
If you want to run this yourself, just change out TickTick to the app of your choice and then ask Claude to rewrite the prompt. So it's not just a task list, the calendar and everything like that. Okay.
Now, here's one where I like this video because Andy's showing that there were problems with it and what he did about them. And there were also surprises. But let's first take a look at what it made.
As you can see, we have TickTick on the left side and we have my task flow here on the right side. It has the task like call the dentist to reschedule right here as well. Pick up dry cleaning.
And if I click on one of them as done, as you can see, it goes down to the completed. Here as well, pick up the dry cleaning, we get a different sound and it goes directly down to the completed tab. You can also see that we have the list here of business, work, personal, fitness and everything like that.
The exact same goes in my app as well. And if we keep going further down, you can see that we have all the tags, errands, family, finance and everything like that, which is just a tagging or a hashtag system. that is working really great.
Just look at errands on both of them. We can click here, click here, and it looks almost identical. Almost identical.
This is the part that I think some of you are going to go into the comments and complain about, and I'd like to hear it if you are really upset about this. And I found out something that actually shocked me. So I don't have the paid version of TickTick.
And so if we click on the calendar view on the side here, it says you have to upgrade now. But on my own app here, if I just open the side, you can see that I click on the calendar view and I actually have full access to it. So REA was actually able to reverse engineer the calendar view as well, even without having access to it because it's written in the code.
So here you can see that the premium only does a sample data. And this is actually real data, which is just absolutely crazy that it was able to do this without looking at the source code. just from the machine binary.
Unreal, unreal. Okay, but there were mistakes and I think it's important to talk about the negatives. So for example, there are some features that aren't included.
Like for example, if I click on do laundry right here, we have a really nice way of writing in the right side. Whereas if I click on do laundry here, We are only able to actually write in one line.
If I click enter, it kind of goes back to the beginning here and I'm not able to create a new line. And so this is where we would have to prompt it again to do that well. The same goes for if we're on today, for example, the colors aren't completely correct.
You can see here the overdue is white. Here the overdue is actually red. You know what?
Let me pause and just say, look, they're clearly mistakes. I'm surprised that the color, which seems like an easy thing to copy, was not copied over. Meanwhile, the calendar, which is behind the paywall, was copied.
So I don't see any rhyme or reason to why things were copied versus not. But it's impressive how much it got copied. And I'm going to jump to Andy's conclusion.
We're able to pretty much reverse the whole app in. about an hour, give or take some extra prompts just to get it to a final state. But the main thing that I really want you to get out of this is this is almost 80 % of the whole app.
And the main benefit of, of course, having your own app like this is that you don't have to pay for it. But the main benefit being that you can build on top of it. That's the thing that people are...
When they get into the legitimate zone, they're saying, look, I like this feature. I want to integrate it. I like this premise for an app.
I want to add to it. Let's look at another. Oh, before we go to another example, I'll just quickly tell you my sponsor is Zapier.
Zapier MCP allows you to save tokens by offloading routine tasks to code. So they're more dependable. They cost less.
And then the intelligent tasks can be handled by AI. I use it all the time to save tokens with my Grok bot, which is my latest obsession. If you use it, there's a link below for you to use and let them know that Andrew sent you.
Let's go on.
this guy just cloned whisper flow let's look at that application we're trying to clone here is called whisper flow now it's a voice to text ai applications and it lives on my desktop app so essentially you can see that this icon right here if i click on it or if i do a hot key is just going to automatically try to translate right try to translate any He means transcribe.
He's saying translate. By the way, Eric does have really nice visuals, don't you think? Speech that I say into proper text.
And he's also able to translate meeting notes, right? So those are really helpful. So what I want to do here is I want to kind of like using that skill and see if we can actually reverse engineer applications on my local machine.
Okay. I've been hesitant about showing prompts, but then again, with something like this, you'll see the prompts are so basic. There is nothing to...
to really hide the, what he is doing, what Eric is doing is actually kind of a smart take on this. Well, let's see, I have prepared a prompt. It's called fine whisper flow on my entire desktop app, right?
That's the folder usery here to basically inspect the app and use the official website as the background. And also explain what you can be approved from the application file. Let me pause on that.
This part I think was really interesting. What can you improve on the app files? I think made a big difference in his results.
And so I want to underline it. Let's keep going. Things like that.
I'm going to get a small working version here working. So I'm going to basically open my cloud here and paste the prompts and just send it over and let cloud here to do the rest. Okay.
look at the right so now you can see that once we have our application is fully complete here if i were to open the app here is what it looks like so we have the exact clone of whisperflow right here in my desktop app so you can see that currently we have all the conversation everything that i said is inside of this i can also click on note taker here to see the past notes that i have took right so i can view the entire transcript or resume if i want to and i can also be able to start to using a shortcut right a short key so i'm going to type in the short key right here he says type but what he means i think is just press the short key that triggers the dictation which is option plus one so i want to start a new application and you can see that we have text here showing okay and that of course is what whisperflow does check out the language though and i can say different languages like uh So you can see that we have English and Chinese here also in the same input, right?
So we can also have the ability here to do that. And it also is really, really fast. So it's not like it takes a long time here to load.
It's transcribed locally on my machine. Let me emphasize that. That is the difference that this prompt that he had improved.
Local dictation, I find to be much faster and safer than sending it to the cloud. And that's why he was able to get a faster result than you usually can get from Whisper. Conversation or the voice here does not go on the internet, which you can see here.
Okay. So as you can see that it's actually using reverse engineering tool here to analyze exactly how that works. And you can see that it's able to creating a similar versions of this using our AI agents.
Okay, again, I'm curious what you think about this. Honestly, because it's not just me farming for comments, though I love to get comments. It's because when I showed this off on Friday's GitHub show and I said this was the top trending repo of the week.
I didn't realize how many people would be upset by that. I think I was very cavalier about it can copy software, ha, ha, ha. And then Adam, a developer who was on with me, said, this seems like a wrong thing to do.
It's like copying the Mona Lisa and selling it or copying the Mona Lisa and using it. I guess that wasn't his analogy. But anyway, you get it.
And a lot of you in the comments came back at me and said, this is wrong. And so I want to know if any of this is changing you or firming you. And if it's firming you up, give me your opinions.
Let's go on to the next one. You can also run R.
Okay, so now we're looking at no longer building, but actually finding. bugs and problems and i think this is going to be a use case that everyone is going to say okay i agree with feature can look fine when you try it once and still break in the rare cases you didn't try and most of those can't be spotted from the code alone it's worth catching these bugs early because if a customer finds a bug while using your app it can cost you that customer to do that you just need to ask claude to use this tool and you need to give it the link to your site then you need to have it check that the feature works exactly the way it's supposed to if anything doesn't work as expected you need to ask it to tell you what went wrong in a full report.
And we asked it not to change anything or read the code so it has to work everything out from the site itself. That way, it can uncover deeper issues that it might miss if it only worked from the code. I don't know of anyone else, by the way, who's talked about this.
I do like AI Labs because their channel does stuff like this. I do wish that it wasn't a disembodied voice. I'd like to get the sense of the person.
It first writes all the test scenarios into a folder, and then it calls the MCP to run them one by one. And if you want to watch the browser while it runs the tests, you can ask it not to use headless mode. This tool runs in headless mode by default, which means you can't see the browser, but you can ask the agent.
to turn it off so you can watch what it's doing once all the tests are done it gives you a full report of every issue it found in our case it reported that the prices shown in our app were different from the prices charged this one wouldn't have been found by looking at the code alone because the pricing code itself looked fine it checked our billing page against the pricing rules we wrote down and the promises on our home page most accounts were priced correctly but two accounts saw one price on screen and got charged another with one seeing half the real total and the other seeing zero it also traced the bugs step by step.
The price on screen gets worked out inside the browser and the line items discount and tax were all correct. So it only goes wrong at the very last step where it adds up the total. It found smaller problems on top of that, like the server accepting a negative number of seats and selling more seats than the plan allows.
All right. Not bad. Okay.
Let's go on to one more. Better than not bad. Here is cloning a video editor.
And the reason I wanted to show what Mihal was doing here is because when it comes to CapCut, I've actually heard a lot of people have problems with TikTok, the company behind CapCut. And they're saying, well, I don't trust it on my computer. If you don't trust it, do you feel comfortable copying it?
Or what Mihal did is not exactly copy it. Well, let's take a look. We will try to reverse engineer CapCut.
By the way, I really love showing off videos like this. This one had, I think, 3000 views. And as I watch it, I go, this really deserves more than 3000 views.
So I should say links to everything below. So I have linked the CapCut location to it. And I'm going to say to reverse engineer this.
And now we wait and see if it is going to reverse engineer or clone CapCut. So Claude is asking, what do you want to understand about? And I'm going to write everything about video editing, captions, animations, layout, transitions.
So we are going to start short and not include everything in one go. Okay. There's something to be said when it comes to CapCut of starting short and not including everything.
It is just packed with so many features that it gets more and more distracting as it gets more and more useful. Okay. Let's see.
A full CapCut is millions of lines. And let's see the results.
Now let's head into our browser and open it up. So this is how it looks. So Claude specifically tried to, you know, not make it very similar to CapCut, but kind of similar, right?
Yeah, this is actually, to call this similar to CapCut is ridiculous. This is similar to any video editing tool. And it doesn't look CapCut -like to me at all.
Okay, so here we have the import option. Let's import the same screen recording which I was doing for this video. okay so now let's try to split it from where i am talking okay so i'm talking from here we're gonna do ctr to split it split option was just like in cap cut delete okay now let's try to use auto captions always the auto caption button right here auto caption english generate done it was pretty fast I'm gonna say that even though he calls it basically a CapCut copy, this is really not.
It's inspired by maybe CapCut, but maybe every other video editing platform or software out there. which actually brings up another another interesting use case what if you just want to be inspired by software no issues there now you have software that inspired your idea and once you start cutting back features and making your own decisions isn't it your own software and therefore you end up with a head start because you're building based on how others have done it I'm wondering what you think about that.
In a more dramatic example I would give you, there was someone who said, look, I don't like the software that comes with my air conditioning unit. I actually want it to be in my Mac menu bar at the top. I made the version of their software that fits in my menu bar.
I don't think there's an issue there, right? Let's look at one last one. This is a software that many of you used.
It's called Loom. And the issue with Loom, of course, is people keep complaining that Loom's prices go up. Here is what Nick did with that.
I've got this thing right here, which is basically the Loom clone that I made from using this repo, right? Like I had to look at Loom. I had to understand how it can work with like the different bubbles.
You can see it does the recording countdown. It might not work because my face cam is recording right somewhere else. So I'll play a clip real quick.
all right so i just wanted to test out how this actually works to make sure that this is like a decent software so i'm going to see if i can pause this and now we can go ahead and keep on rolling i can move this thing around i can also make it smaller or larger while i'm recording that's very nice and let's go ahead and stop see what happens but the thing that's important to realize is that we didn't clone loom this is a very different looking app we didn't clone like all of the exact ui and the design elements we cloned the functionality we understood how does the little bubble work how can you move it around how can you change the window that you're recording right like we talked about this sort of stuff and we had to analyze that sort of stuff loom obviously records and stores your things in the cloud and looms cloud but this one is just local so it's storing these files in my own folder inside of this app called her recorder Okay, so there you have it.
Super easy. Most of these have taken minutes. All, I think, under an hour.
Very easy to copy their prompts and copy software that you have. What do you think of this? Again, let me know in the comments.
And if you like this one, you should know that this was the number one repo of the week last week. And there were nine others that were super impressive that I didn't break down in this level of depth, but I did show you how they work. And I think you should go check those out next.
I'll see you in there.
The Hook
The bait, then the rug-pull.
Everyone's talking about an insane new way to copy software, and the host has used it enough to want a verdict: watch five real demos reverse-engineering closed-source apps, then decide for yourself whether this is a legitimate productivity hack or a line nobody should cross.
Frameworks
Named ideas worth stealing.
03:31model
REA pipeline: Agent to Evidence
Agent
REA (MCP)
Hopper / Ghidra / IDA / JS analyser / Browser
Evidence
The agent calls REA over MCP, REA dispatches to whichever underlying reverse-engineering tool fits the question, and the result is written out as an evidence file the agent can build from.
Steal forexplaining any agent-plus-tool-wrapper architecture, not just reverse engineering
CTA Breakdown
How they asked for the click.
VERBAL ASK
09:15link
“If you use it, there's a link below for you to use and let them know that Andrew sent you.”
Read mid-roll after the first two demos, folded into a transition line ('before we go to another example'), with a personal referral ask rather than a hard sell.
Add Modern Creator as a preferred source and Google shows you more of our breakdowns in Search, Top Stories, and AI Overviews. It only changes what you see, and you can undo it in your Google settings anytime.
Add to Preferred SourcesOpens your Google source preferences with us pre-loaded. Tick the box and you're done.
Andrew Warner sits down with Matt Pocock to unpack the Claude Code skill library that passed 200,000 GitHub stars, and the small habits of alignment, pruning, and teaching baked into it.
Andrew Warner spends a day cramming on "agent loops," then brings Matthew Berman on screen-share to react to five other creators' examples before showing off — and fixing — his own.
Two hosts run through ten GitHub repos and skills that fix one narrow AI-coding annoyance each, then argue about whether skills are already becoming obsolete.
A weekly roundup episode where the host and a Zapier guest run through ten open-source repos built to pair with a coding agent, from screenshot-to-code to a proxy that cuts terminal noise by up to 90 percent.
Two hosts count down the week's ten hottest GitHub repos, from a security-scanned Claude plugin index to a self-hosted finance tracker wired to 2,500 banks.
00:16
00:36
00:50
01:04
01:25
01:34
02:02
02:16
02:33
02:48
03:03
03:12
03:50
04:09
04:20
04:39
04:54
05:10
05:26
05:58
06:14
06:30
06:46
07:16
07:31
08:04
08:21
08:38
08:54
09:11
09:28
09:39
10:27
10:50
11:12
11:35
11:57
12:20
12:42
13:05
13:28
14:03
14:19
14:42
14:45
15:07
15:23
15:39
15:47
16:11
16:30
16:48
17:05
17:32
18:00
18:18
18:36
18:54
19:12
19:33
19:45
19:55
20:09
20:24
20:38
21:02
21:07
21:12
Video of the Day29:45
35:11
22:57
27:32
13:57
18:45