Browser: allow config default for efficient snapshots #1336
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.
Summary
browser.snapshotDefaults.mode(currently supports"efficient") to the config schema/typesWhy
We want a configuration switch that makes efficient snapshots the default only when explicitly configured, so operators can reduce snapshot size/noise without forcing all callers to pass
mode=efficientin every tool call or CLI invocation.Why this approach
browser.*because it controls browser snapshot behavior, not agent policy or tool gating.mode: "efficient"for now to minimize scope while matching existing behavior; the config does nothing unless explicitly set.Tests
pnpm test -- src/agents/tools/browser-tool.test.ts