Jun retweeted
Most browser-agent problems show up after the happy path.
Run two. Same site. Same account. New IP. Lost session. Unclear spend. Trace that does not tell you enough.
Everything we shipped last week to solve this. ↓
Jun retweeted
Launch week -> Day 05
Today, we're rolling out simpler pricing.
Launch, Scale, Enterprise. Metered browser rates, usage credits, visible limits, and a usage dashboard that shows spend before the bill arrives.
🧵
Jun retweeted
Launch week → Day 02
Today, we're rolling out Dedicated IPs
A stable network origin for agents that log in once and need to keep running from the same place.
🧵
Jun retweeted
Launch week → Day 01
Today, we're rolling out Stealth Browser
Our own fork of Chromium - fortified at the source code level to access the hardest sites to bypass on the web.
🧵
Jun retweeted
Stop paying for a browser after the work is done or your agent dies.
Steel sessions now take an inactivity timeout: if the agent stops driving the browser for the window you set, Steel releases it and the meter stops.
Read more ↓
Jun retweeted
Most of what you ship to an agent gets compressed before it acts — docs, SDKs, blog posts, distilled by the model first.
Errors are the exception. They reach the agent intact.
We've been rebuilding ours around that. ↓
the practitioner angle If you're building browser or computer-use agents, this is the fastest way to see who's actually ahead, and how each number was scored. Read past the top row.







