Repository navigation
Add web-fetch usage fields to inference breakdowns - #395
Merged
Merged
Conversation
Contributor
Author
|
This PR was generated with Warp. Comment    |
Xavientois
reviewed
Oct 9, 2026
Xavientois
approved these changes
Oct 9, 2026
1 task done
szgupta
approved these changes
Oct 9, 2026
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
2 participants
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.
Description
Add presence-capable fetch-page count and cost fields (US cents and credits) to
InferenceUsage, with generated Go bindings. Pages mean URLs requested by native fetch calls, not successful responses. Existing field numbers stay unchanged; absence remains distinct from recorded zero.Justification
Web fetch contributes to inference charges but has no breakdown component. This is the additive schema prerequisite for the warp-server web-fetch base layer under REMOTE-3430. Consumed by warp-server#19455; cross-repository prerequisites cannot form a native GitHub stack.
Validation passed with protoc 36.1 and protoc-gen-go 1.36.6:
./script/generate -a multi_agent -v v1,go test ./...andgo vet ./...inapis/multi_agent,npm ci,npm run generate:ts,cargo build, andcargo test. The TypeScript package tarball import and CI’s version-comment-excluding generation clean-diff check also passed. Rust and Go currently contain no tests. Unrelated compiler-header churn was excluded.Sensitive Fields
sensitive. No string fields added.Native stacks: schema 395 → 396; server 19455 → 19459. The upper server layer pins the fallback schema; the lower server layer pins the fetch schema.
Plans: