How we let an agent use a browser without breaking things
Session isolation, replayable runs, and why every click is written down.
James Smith
•
6 min
Some tasks only exist behind a web form: a state filing portal, a registrar without an API, a supplier’s order page. To finish those, the agent has to drive a real browser, and browsers are messy.
One session per task
Every task runs in its own isolated browser session with only the credentials that task needs. Nothing is shared between tasks, so a stuck page or a stray cookie can’t leak into the next job.
Every click is written down
The agent records each step as a replayable log of what it saw and what it clicked. When a run fails, we can replay it exactly, and so can you. When a vendor changes their form, the replay shows where the old path broke.
If the agent reaches a step it can’t safely complete, it stops and hands the task back with the log attached instead of guessing.
Keep reading
Approvals
8 min
The approval is the product: designing trust into an agent that spends money
We shipped an agent that could file an LLC in eleven minutes and nobody used it. Here's what we changed - and what founders actually want to see before they say yes.
Read more
Launch playbooks
6 min
The 72-hour launch: what actually has to happen first
The order matters more than the effort. A sequenced checklist from name to first customer.
Read more
A smarter way to
build a company
Skip the endless research, planning, and setup. Vaxnori AI works alongside you to create your brand, organize your launch, and handle the operational details.
