You all saw it right, Claude has restricted REA for most the the people.
So after a weeks worth of testing, here is a ethical way to bypass that..
feel free to read this short guide.. https://x.com/i/article/2119733520436498432
Bypassing the AI restrictions the ethical way (Short guide)
Last week i made a post where i was just angry about the changes but they made it even worse..
so here is my two takes on it and how i basically nullify it and proceed with my own use.
this will be 100% patched either by them adding more rules or something else so here is the lore drop before it get's patched.
also yesterday they made the rule worse by them adding more rules like you now can't even create a close recreation which is utterly bullshit rule.
after a lot of digging last week spending more than 100hrs, my results are still the same.
Green hat kid ported in less than 2 days. (60 FPS + On a Mac using this..)
the two repos that got killed after this rule update for most people are:
1- REA: Reverse Engineer Anything
2. GHIDHRA- Reverse Engineering Framework
Now the easiest way to explain how they work is in my last article..
this won't do that, you all are here for the sauce, so here it is.
we are going the opposed way, the real fix part.
some people say "a cure to a poison can be found in the poison itself". what we are doing here is using the cure to create poison.
we are now going to be using BLA, it will find the fix in itself.
how it works is simple.
BLA : Brings noise in the mix (Mixing it with REA, now this is a killer combo, BLA(Cure) act's first then you can use REA(Poison) to create an app).
this works 100% of the time..
this is the simple sauce & links in the first comment...
| Bookmark this Short guide if you don't want to restrict your AI - @Motion_Viz