Reverse engineer anything with agents, from app behavior down to native binaries.
TypeScript agent-skillsai-agentsbinary-analysisclaude-codeclicodexcordisdecompilerdeveloper-toolsdshdsh-pluginghidrahopperllmmcpmodel-context-protocolreareverse-engineeringstatic-analysistouhou
docs(website): use straight quotes in model essay
N0zoM1z0806ff575676e
diff --git a/website/public/blog/reverse-engineering-models/index.html b/website/public/blog/reverse-engineering-models/index.htmlindex 0ec0f9a6f..2b3c4c1ce 100644--- a/website/public/blog/reverse-engineering-models/index.html+++ b/website/public/blog/reverse-engineering-models/index.html@@ -426,8 +426,8 @@</p><p><strong- >“The model did not know that compiler quirk” and “the model- could not use it” are different problems.</strong+ >"The model did not know that compiler quirk" and "the model+ could not use it" are different problems.</strong>Retrieval may solve the first, but turning that fact into a usefulcandidate still takes work. And if the candidate fails, the model@@ -688,7 +688,7 @@already had the target's 1,825-byte length, yet 467 byte positionsdiffered. Even a byte-difference count can change abruptly when abranch encoding changes. Such diagnostics can guide the next- experiment, but I would validate any reward for “getting closer”+ experiment, but I would validate any reward for "getting closer"against the full acceptance check.</p><p>