Repository navigation
Add an aggregate decision for noisy guided comparisons - #329
Merged
Merged
Conversation
improve start --decision aggregate freezes a rule that judges speed or cost across all pairs: the median paired improvement must meet the frozen minimum, more pairs must improve than regress, and the other metric's median regression must stay within its allowance. Completion, quality and non-performance gates stay strict on every pair. Reports add the counts and a non-gating one-sided sign-test p-value. The default per-pair decision and its messages are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
AgentLoop replay self-testThis required repository check evaluates generated synthetic demo traces. It tests the replay and CI machinery; it does not show that this PR improves application performance. AgentLoop CI Report
Performance Gates
Trace inputsThis comparison includes synthetic data. It does not establish application performance gains from a pull request.
Metric Impact
Top Findings
|
Merged
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.
Why
improve finishrejects a change if any single pair is slower. Agents that call hosted models vary from run to run. In the first Codex run (docs/CODEX.md), a change that cut tokens in most pairs was rejected because two pairs were slower. Real agent changes will often be rejected by chance under that rule.What
agentloop improve start --decision aggregate(defaultper-pair). The decision is stored in the hashed session, so it cannot be changed after results are known. Sessions from older versions keep per-pair judgment.--minimum-improvement;report.jsongains adecisionobject with counts, the median, reasons and a one-sided exact sign-test p-value, which is reported but does not gate. Markdown, HTML,plan.mdand the CLI summarize it. Per-pair failures are still visible in each case's gate table.decision: {mode: per_pair, passed: true}is added to the report.Tests
test_improvement.py, guided validation, docs site, published README and Codex runner tests: 61 passed, 1 skipped. Pre-commit is clean.🤖 Generated with Claude Code