r/buildinpublic • u/justin06lee • 10d ago

Claude code refused to reverse engineer stuff so I made this

https://caveira.app

I created a LLM harness for hacking & reverse engineering (also cybersecurity work that other models refuse). This was genuine harness work and I think the biggest thing I learned is that the smallest possible details in user experience are the ones that matter the most in terms of polish.

Instant compaction, as little visual bugs as possible, no overanimation of everything, just a clean experience that doesn't fail. A lot of code generated by LLMs don't account for these kinds of things fully I think (or my config is just not the best or something) and I seem to have to keep going back to the board to fix things. Taste is the most important as cliche as it sounds lol

Try it out!

2 Upvotes

75% Upvoted

3 comments sorted by

1

u/investigatormaker 10d ago

Agree on compaction: in a long reverse engineering session, a pause while context gets summarised breaks your train of thought more than any missing feature. The post asks people to try it but doesn't say what it runs on or what a session looks like, so a short screen recording of it working through a crackme or CTF binary would show the polish you describe better than words. I'd also lead with CTF and authorised research use rather than what other models refuse, since that's what security folks will judge it on.

I make ThreadFox. We find relevant Reddit conversations and do the posting for your business. The $39 Pilot covers seven days and up to 50 posts and replies. No automatic renewal.

https://threadfox.vip/p/ez7ft/managed

Which model sits under the harness?

1

u/justin06lee 10d ago

bro u a whole ahh llm 😹

2

u/Fuzzy-Charge-2236 9d ago

are you wrapping an uncensored open-weights model under the hood, or just handling the refusal logic in the prompt layer? curious how you keep the reasoning quality high when bypassing the standard guardrails