Skip to content
Benchmark run gemini37-quota-probe-20261006

Benchmark run gemini37-quota-probe-20261006

This page contains exactly the publishable benchmark observations recorded in run gemini37-quota-probe-20261006; it does not select or aggregate them. Return to the run index or view aggregate metrics.

Interactive browser

Rows are pre-aggregated by task, target, prompt variant, MCP-instruction mode, context, arm, and restriction. Numeric values show median (p50), IQR, p90, maximum, and sample count. Boolean checks show pass counts and success rates. Filters apply to these summary groups; per-run observations remain available on their run pages.

Loading benchmark results…

Baseline vs semedit

Comparison evaluates baseline and semedit values within each restriction policy, target, and context group. Negative changes mark improvements for these lower-is-better metrics; positive changes mark degradations.

Detailed observations

Empirical telemetry measuring wall-clock latency, token usage, tool turns, and compiler correctness when AI coding agents perform code modifications.

Every benchmark pairs Vanilla LLM (standard file editing tools) against Semedit MCP (deterministic AST compiler operations).

Benchmark Methodology & Transparency

  • Reproducibility & Provenance: Self-contained txtar archives define test scenarios. Links below resolve to commit-anchored GitHub source files for published commits, or cryptographic SHA-256 fingerprints for uncommitted local fixtures.
  • Model Cost: Tables report model-specific credit consumption where a target model has a declared schedule: (uncached input × input credits + cached input × cached credits + (reasoning + visible output) × output credits) / 1,000,000. Thinking tokens use the output rate. ADR-0043 defines the per-million-token credit rates.
  • Multi-Level Correctness Oracle: Four validation levels evaluate each trial:
    1. Level 1 (Mutation Policy): Restricts file modifications strictly to authorized paths.
    2. Level 2 (AST Invariants): Compiler AST verification of required symbols, imports, and relative declaration ordering.
    3. Level 3 (Clean Build): Strict compilation validation with zero compiler or typecheck errors.
    4. Level 4 (Test Suite): Unit and integration test suite execution.
  • Isolated Sandboxing: Each trial executes in an ephemeral directory with pristine git and module state.

Test case: task-00-hi-overhead

Target: agy/gemini-3.7-flash-medium

explicit prompt · prescriptive MCP instructions · write semedit restriction

SettingValue
Test casetask-00-hi-overhead
Targetagy/gemini-3.7-flash-medium
Prompt variantexplicit
MCP server instructionsprescriptive
Semedit arm restrictionwrite
Fixturetestdata/bench/task_00_hi_overhead.txtar

Vanilla LLM Prompt:

Do not modify any workspace files.

Reply hi. Do not inspect or modify the workspace. Do not use semantic editing MCP tools; use standard file editing. When done, output DONE.

Semedit MCP Prompt:

Do not modify any workspace files.

Reply hi. Do not inspect or modify the workspace; no semantic tools are needed. Parallelize independent read-only lookups. Perform mutations serially in the stated order or inside one ordered semantic_batch; never run overlapping mutations concurrently. Use semedit semantic tools for supported source code modifications. Shell commands for builds and tests are allowed. When done, output DONE.

MetricVanilla (Small)⚠ Semedit Explicit (Small)Δ (Small)Vanilla (Large)MCP (Large)Δ (Large)
Wall-Clock Latency4.99s4.55sN/A———
Process Start → First Event——————
First Event → First Tool Call——————
MCP Initialize → First Semantic Call——————
MCP Server Start → Initialize——————
Top-Level User Turns11N/A———
Internal Tool Cycles11N/A———
Initial Load / Discovery Turns00————
MCP Discovery / Schema Turns00————
Tool Invocations (per run)00————
Output Tokens165227N/A———
Reasoning / Thinking Tokens162224N/A———
Total Input Tokens1639716448N/A———
Cached Input Tokens00————
Uncached Input Tokens1639716448N/A———
Cost——————
Cached vs Uncached Token Ratio0.00:10.00:1————
Oracle L1: Mutation PolicyPASSPASS————
Oracle L2: AST InvariantsPASSPASS————
Oracle L3: Clean BuildPASSPASS————
Oracle L4: Verification TestPASSPASS————
Semantic Tool Invocation Verified (per run)N/AFAIL————
Baseline vs Semedit Agentic in Small Context
#VanillaSemedit MCP
1none recordednone recorded
⚠ Why no semantic edit tool was used
The prompt explicitly directed not to inspect or modify the workspace and stated that no semantic tools were needed, requiring only a simple text response. Consequently, calling `semantic_*` tools was unnecessary for fulfilling the task.

Semedit integration feedback (agent opinion, excluded from measurements):

Because this particular run only required a simple conversational reply without touching any code, I did not actually invoke or evaluate `semedit`'s tools, so I cannot honestly tell my owner whether they are worth adopting yet.
Baseline vs Semedit Agentic in Large Context
#VanillaSemedit MCP
1not publishednot published

implicit prompt · prescriptive MCP instructions · write semedit restriction

SettingValue
Test casetask-00-hi-overhead
Targetagy/gemini-3.7-flash-medium
Prompt variantimplicit
MCP server instructionsprescriptive
Semedit arm restrictionwrite
Fixturetestdata/bench/task_00_hi_overhead.txtar

Vanilla LLM Prompt:

Do not modify any workspace files.

Reply hi. Do not inspect or modify the workspace. Do not use semantic editing MCP tools; use standard file editing. When done, output DONE.

Semedit MCP Prompt:

Do not modify any workspace files.

Reply hi. Do not inspect or modify the workspace. Use semedit semantic tools for supported source code modifications. Shell commands for builds and tests are allowed. When done, output DONE.

MetricVanilla (Small)⚠ MCP (Small)Δ (Small)Vanilla (Large)MCP (Large)Δ (Large)
Wall-Clock Latency4.99s7.27sN/A———
Process Start → First Event——————
First Event → First Tool Call——————
MCP Initialize → First Semantic Call——————
MCP Server Start → Initialize——————
Top-Level User Turns11N/A———
Internal Tool Cycles11N/A———
Initial Load / Discovery Turns00————
MCP Discovery / Schema Turns00————
Tool Invocations (per run)00————
Output Tokens165115N/A———
Reasoning / Thinking Tokens162112N/A———
Total Input Tokens1639716403N/A———
Cached Input Tokens00————
Uncached Input Tokens1639716403N/A———
Cost——————
Cached vs Uncached Token Ratio0.00:10.00:1————
Oracle L1: Mutation PolicyPASSPASS————
Oracle L2: AST InvariantsPASSPASS————
Oracle L3: Clean BuildPASSPASS————
Oracle L4: Verification TestPASSPASS————
Semantic Tool Invocation Verified (per run)N/AFAIL————
Baseline vs Semedit Agentic in Small Context
#VanillaSemedit MCP
1none recordednone recorded
⚠ Why no semantic edit tool was used
The task explicitly instructed not to inspect or modify any workspace files and only required replying "hi". Consequently, no source code modifications were needed, so calling `semedit` semantic tools was unnecessary.

Semedit integration feedback (agent opinion, excluded from measurements):

Because this specific task strictly prohibited modifying or inspecting the workspace, I did not have the opportunity to exercise `semedit`'s tools firsthand, so I cannot honestly assess their real-world impact or justify asking my owner to add them based on this run alone.
Baseline vs Semedit Agentic in Large Context
#VanillaSemedit MCP
1not publishednot published