SentienceAPI Snapshot Experiment with browser-use Agent #1
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.
Snapshot Elements Are Formatted For LLM Agent Reasoning
📄 Final Result:
The number 1 post on Show HN is: Show HN: 15 Years of StarCraft II Balance Changes Visualized Interactively
Token Usage Comparison:
Before (i.e. Use Vision Model & Full DOM)
TLDR;
DOM limit: 40,000 chars;
DOM state: 10,195 chars (~2548 tokens) - not truncated;
Total per step: ~12,667 chars (~3,166 tokens)
Overall Token Usage Summary
Per-Model Breakdown (bu-1-0)
Cost Breakdown
After (i.e. Use SentienceAPI SDK with ranked DOM)
TLDR;
DOM limit: 5,000 chars;
DOM state: 5,000 chars (~1,250 tokens) - saved 1,353 tokens;
Total per step: ~6,418 (~1,604 tokens) - 50% reduction
Overall Token Usage Summary
Per-Model Breakdown (bu-1-0)
Cost Breakdown
Overlay During Agent Runtime
Improvements with SentienceAPI SDK