Skip to content

Record fetching backend per URL in run reports#306

Open
probably-jaden wants to merge 1 commit into
mainfrom
feat/report-backend-per-url
Open

Record fetching backend per URL in run reports#306
probably-jaden wants to merge 1 commit into
mainfrom
feat/report-backend-per-url

Conversation

@probably-jaden

Copy link
Copy Markdown
Contributor

Adds a backend field to each entry in reports/<run_id>.json: the fetcher recorded on the stored capture (set for stored/deduped/cache_hit outcomes, "" when nothing was fetched, e.g. errors).

This makes per-domain cost attribution possible downstream — you can join a run report's URLs against which backend (self-hosted browser vs a paid API) actually fetched them. Cost estimation itself (cost.py) is unchanged; read_outcomes and the coverage report are unaffected since they only read url/status.

Tests: code_tests/unit_tests/test_agents_and_tools/test_source_archive/ — 131 passed (new test covers stored/cache_hit/error rows).

🤖 Generated with Claude Code

Add a "backend" field to each entry in reports/<run_id>.json: the
fetcher recorded on the stored capture (set for stored/deduped/
cache_hit outcomes, "" when nothing was fetched, e.g. errors). This
lets downstream tooling attribute per-domain cost by backend without
changing the cost estimation itself.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

1 participant