Skip to content

feat: add efficiency regression metrics (calls, latency, tokens) (#114) - #149

Draft
askmy-stack wants to merge 1 commit into
mainfrom
cursor/efficiency-metrics-c2a5
Draft

askmy-stack wants to merge 1 commit into
mainfrom
cursor/efficiency-metrics-c2a5

Conversation

@askmy-stack

Copy link
Copy Markdown
Owner

Summary

Implements #114 — efficiency regression metrics that track operational cost (tool calls, retries, latency, tokens, optional model cost) without replacing correctness in pass/fail.

Changes

  • New tool_semantics.efficiency module: EfficiencyMetrics, compare_efficiency, aggregation, fixture loading, markdown ## EFFICIENCY section
  • Relative deltas (e.g. tool calls 8→31, latency +94%) with configurable regression thresholds
  • append_efficiency_section for eval/probe reports when metrics exist
  • Fixture: examples/efficiency/sample_metrics.json
  • Docs: docs/efficiency.md, link from docs/probes.md

Test plan

  • pytest tests/test_efficiency.py
  • ruff check / mypy on new module
  • CI green

Closes #114

Open in Web Open in Cursor 

Track operational cost alongside correctness with relative deltas.
Efficiency is informational only and never drives pass/fail alone.

Co-authored-by: Abhinaysai Kamineni  <askmy-stack@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[P2] Efficiency regression metrics (calls, retries, latency, tokens)

2 participants