The latest articles on DEV Community by Bill E BoB (@bill_ebob_708b7615aed804). https://dev.to/bill_ebob_708b7615aed804 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4077797%2F6c6c8ac5-53d6-4b8a-801d-66ba1393436f.png https://dev.to/bill_ebob_708b7615aed804 en Bill E BoB Fri, 14 Aug 2026 13:50:27 +0000 https://dev.to/bill_ebob_708b7615aed804/kryptic-a-local-first-ai-engineering-agent-that-verifies-before-it-claims-success-3gop https://dev.to/bill_ebob_708b7615aed804/kryptic-a-local-first-ai-engineering-agent-that-verifies-before-it-claims-success-3gop <p>Most coding agents optimize for producing a plausible answer quickly. Kryptic is built around a different question: can the result be verified, repaired, and safely rolled back on the user’s machine?</p> <p>Kryptic is a local-first, open-source Node.js CLI for AI-assisted engineering work. It runs in a bounded workspace and keeps the execution loop explicit:</p> <ol> <li>Plan the requested change.</li> <li>Act through constrained tools.</li> <li>Verify with real execution results.</li> <li>Repair only when verification identifies a concrete failure.</li> <li>Stop with an auditable result.</li> </ol> <p>The important distinction is that verification is not model prose. A model can say that a test passed; Kryptic treats the command’s exit status, captured output, resulting diff, and workspace state as the evidence. If the evidence is missing or contradictory, the step is not complete.</p> <h2> Safety boundaries </h2> <p>The current release includes several defensive choices intended to make failures recoverable rather than mysterious:</p> <ul> <li>Direct process execution instead of passing commands through a shell.</li> <li>Literal patch replacement to avoid broad or ambiguous file corruption.</li> <li>Workspace and secret-file boundaries.</li> <li>Approval-gated edits and transactional rollback.</li> <li>Path revalidation before rollback operations.</li> <li>Provider timeouts and interrupted-run resume.</li> <li>An origin-restricted browser bridge with optional token authentication.</li> <li>A guided first-run setup that stores provider secrets in a protected user-level file.</li> </ul> <p>These controls are deliberately less glamorous than a confident agent transcript, but they make the system easier to inspect and test.</p> <h2> Reproducible evidence </h2> <p>Kryptic currently has 42/42 regression tests, 11/11 deterministic benchmark cases, and 11/11 offline-demo checks in the local release workflow. Those numbers describe Kryptic’s own checks; they are not fabricated cross-agent comparisons. The comparative task definitions are published so that future evaluations can use the same fixtures and report failures honestly.</p> <p>The project also includes an offline demo that requires no API key. It exercises the plan–act–verify–repair shape without depending on a hosted service, which makes it useful for first-run testing and CI.</p> <h2> What I’m looking for </h2> <p>I’m interested in feedback from developers who build or use coding agents. In particular:</p> <ul> <li>Which safety boundaries are missing or too restrictive?</li> <li>What verification fixtures would make agent comparisons fair?</li> <li>Which failure cases should be included in a public benchmark?</li> <li>Does the first-run setup explain the local-first model clearly?</li> </ul> <p>Kryptic is early, and I’m not claiming it is universally better than other agents. The goal is narrower and more measurable: make engineering agents prove what they changed, show how they verified it, and recover transactionally when the first attempt fails.</p> <p>Repository: <a href="https://github.com/adnqcr7-code/kryptic" rel="noopener noreferrer">https://github.com/adnqcr7-code/kryptic</a></p> opensource ai security