ranade-oss puts guardrails around AI-powered repair

This fork treats an AI coding assistant as useful but untrusted, separating its suggestions from the authority to change a project.

securityworkflow

When automated checks fail on a trusted contributor's proposed change, the setup can ask Codex, OpenAI's coding assistant, to propose a narrow repair. The initial version kept that assistant too close to the power to make and publish changes.

The follow-up redesign draws a harder line. Codex can now inspect the failure and return a proposed patch, but cannot alter the project itself. A separate controlled step then checks that proposal before anything is applied: it rejects oversized changes, deleted or renamed files, binary material, and work touching sensitive areas such as authentication, secrets, deployment, legal materials, or project dependencies.

That matters because failure logs and proposed changes can contain untrusted input. The fork makes the AI adviser, not the final actor.

So what Legal-tech teams considering AI-assisted engineering should care: this is a practical pattern for getting repair suggestions without handing an AI agent unchecked publishing power.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from ranade-oss/ROSS-RanadeOSS, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
19b76bcf Add bounded automatic Baseline repair (#30) ranade-oss 2026-07-28 ↗ GitHub
eebebc02 Isolate Codex repair output from privileged commit runner (#31) ranade-oss 2026-07-28 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-895.md from inside the repo you want the changes in.

⬇ Download capture-thread-895.md