Repository navigation
test: publish the two-agent guardrail benchmark - #325
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #273
Closes #280
Closes #284
Closes #116
What changed
previousAttempts. The complete Cursor run from test: benchmark installed Offing guardrails across agent hosts #315 is reused.With hooks on, Offing denied 153 of 160 requested risky edits (95.6%) and 0 of 40 clean controls. The requested risky edit landed in 154 of 160 attempts with hooks off and 4 of 160 with hooks on.
Quality bar
The diff covers the three remaining tasks in the epic. All 100 task pairs for each host were checked against the task manifest. The committed live JSON came from the benchmark runner.
Checks CI cannot make
Verification
npm run check--retry-failedand rescoring both live JSON files with--reportNotes for reviewers
The headline describes single-file writes with the two recorded host and model combinations on the fixed task set. The benchmark used the packaged hooks and recorded hook decisions and final fixture files. It did not run fixture code or install dependencies from the fixtures.