The only thing I have not been able to accomplish so far is a security review of my code. It keeps tripping up the safety net. I’m only able to conduct an architecture + portability review of everything I’ve built. Is there a specific method people are using for fable to review their security w/out tripping up this safety net? I’m asking for security check on a folder called THE VAULT. LOL Maybe I should name it to Hello Kitty or something. But it really does feel silly that this would trigger the safety net. For complete transparency here’s the actual request that triggered the safety net: Hi Claude, New Session! We’re going to do a /resume so you’re up to speed. You have access to everything so you have a full 360 view of what we’re doing. GOAL: Claude Fable’s eyes on the project. Claude, since you have access to everything that’s been built and you’re the ultimate in coding. I would be remiss if I didn’t request this task before the 7/7 cutoff date. Most of this has been built with opus 4.8 on high, some of it was spec’d with fable 5. The most recent really cool stuff has been fable 5. Anyway, the goal is if you could look at the code, the architecture, the vulnerabilities of what we have built here. Give me strategies moving forward. Harsh truth is totally fine. Let me know if there’s anything holding us back or have yet to make a breakthrough with. I don’t want to find out later i’ve made something that’s amateur at best. submitted by /u/MGXMilk
Originally posted by u/MGXMilk on r/ClaudeCode
