Blog
Thoughts on AI browser agents, browser automation, and building dassi.
-
Cloud Browser Agents Boot a Second Chrome in a Datacenter
A new energy-economy model says AI productivity gains raise net CO₂. Cloud browser agents prove the point: a second Chrome for work your own tab already did.
-
Atlas Is Gone. The $200-a-Month Price It Normalized Isn't.
OpenAI is winding down Atlas, but the $200 browser-agent tier lives on at Comet, Claude and Genspark. dassi does the job in your own Chrome from $10.
-
Can AI Agents Log In to Websites? Yes, but It Matters How
Yes. AI agents log in to websites three ways: you give them your password, you sign in inside their cloud browser, or they use your own logins and password manager.
-
PrismML Wants a Small Language Model to Replace Frontier AI. Context Is the Missing Half.
PrismML's tiny LLM bet only works when the model stops guessing. A browser agent reading your logged-in tab needs far fewer parameters than a blind cloud one.
-
Onboarding an AI Teammate Means Handing It Logins It Can't Use
Disrupt 2026 pitches AI agents as your next hire. Onboarding a human means 15 logins on day one. Onboarding an agent means API keys for the three with APIs.
-
Where to Launch Your AI Startup in 2026: Top Directories, Launchpads, and Communities
A comprehensive guide for AI founders on where to launch, build early traction, and earn high-authority backlinks across top directories in 2026.
-
Meta Built an AI Agent That Fills Out Meta's Forms
Meta shipped an AI agent for WhatsApp Business onboarding — inside Meta's dashboard. Vendor setup agents stop at the property line. A browser agent doesn't.
-
Botsitting Is Real. Most of It Is You Logging In Again for a Robot.
The botsitting critique measures supervision time, but most of that time is re-authenticating and re-explaining context to an agent that opened a blank browser.
-
Your Browser Agent Connected to Chrome. Just Not the One You're Logged Into.
Your agent says connected, then hits a login wall. It attached to the wrong Chrome profile. How to read chrome://version and fix the user-data-dir mixup.
-
Anthropic Wants to Slow AI Down. Your Browser Agent Is Still Logged Out.
Anthropic's CEO wants to slow AI down. But model capability never blocked your browser agent. Session state did, and a fresh cloud Chrome has none of it.
-
Mecka Is Raising $500M to Teach Robots What a Kitchen Is. Your Browser Already Knows You.
Mecka AI is raising ~$500M for robot training data because robots have no real-world context. Your browser already has yours. Most AI agents throw it away.
-
OpenAI Stopped Selling Pro. A BYOK Browser Agent Never Noticed.
OpenAI paused new Pro subscriptions over Astra demand. If your assistant is wired to one vendor tier, their capacity ceiling becomes your outage.
-
They Wanted $100/Month for a CSV Button. The Data Was Already on My Screen.
A SaaS tool wanted $100 a month more to unlock CSV export. So a browser agent read the rendered table in my already-logged-in tab and wrote the file instead.
-
Hackers Are Reselling Stolen Claude Tokens. Rotating Your Key Won't Save You.
Attackers are lifting Claude session tokens off subscribers' machines and reselling the access. The fix isn't rotation, it's counting where your keys live.
-
Publishers Sued OpenAI Again. Your Browser Reads What You Already Pay For.
Seattle Times and Newsday sued OpenAI over how crawlers got their content. A browser agent never touches that pipeline: it reads the tab you already pay for.
-
Three Browser Agents Hit HN Today. None of Them Get Past Okta.
Open-source browser agents boot a fresh cloud Chrome and stall at your Okta login. What breaks at each SSO step, and why session state is the real blocker.
-
Gemini Planned a Hike From Memory. The Trail Conditions Page Was Right There.
Hikers got rescued after planning a route with Gemini. The model recalled a plausible trail instead of reading the live conditions page. Same failure hits work.
-
Nscale Wants $3.5B for AI Compute. Your Chrome Is Already Running.
Nscale is chasing $3.5B in pre-IPO financing. Every cloud browser agent rents a datacenter Chrome you eventually pay for. Yours is already open and logged in.
-
Meta Is Paying People to Watch Them Use Its AI. A Browser Agent Doesn't Need To.
Meta is paying users to observe their AI sessions. A browser agent reads the tab you're already logged into, locally, and with BYOK nobody has to buy context.
-
Palo Alto Paid $500M to Give Agents Secrets. Mine Doesn't Get a Password.
Palo Alto paid $500M to give AI agents credentials. A browser agent in your already-logged-in tab never needs one. What it sees is session state, not secrets.