What it is
Tabruns is a Chrome side panel. You ask for something in ordinary words — “fill this in with my details”, “where do I cancel this?” — and it reads the page you are on, works out the steps, and either answers, walks you through them, or carries them out in your own browser session.
It is not a separate browser, a headless robot, or a service that logs into things on your behalf somewhere else. Every click and keystroke happens on your screen, in your tabs, with your logins, while you watch.
Why it exists
The web is full of forms nobody wants to fill in twice, settings buried four screens deep, and unsubscribe links that move. All of it is mechanical, and all of it still lands on a person.
The reason an assistant has not simply taken that over is trust, and trust is a design problem rather than a model problem. Something that can type into your bank's website has to be legible: you should be able to see what it intends before it does it, watch it happen, stop it, and put it back. That constraint shaped everything below.
The three rules
You see the plan first
Every run is shown before it starts, with the exact values it will type, where each one came from, and which required fields it is leaving alone.
Consequences wait for you
Anything that submits, publishes, sends or spends is named as such and never starts itself — in every mode, on every round. Not even a spoken “go ahead” opens that gate.
It reads shape, not content
Field names and control kinds leave your browser to build a plan. The values in them do not, and passwords and card fields are never read at all.
How a run actually works
- The extension describes the page: what controls exist, what they are called, which are required. No values.
- That description and your request produce a step-by-step plan, checked against a schema before anything is allowed to run.
- You approve it — or it starts straight away, if you have said that is fine and it contains nothing consequential.
- The extension carries it out on the page, reading each value back to confirm it actually landed, and reporting the ones that did not.
The mechanics are covered properly in the Help Center — 24 articles, including what to do when a page does not behave.
Where it is today
Honestly: early, and working. The planner and the run engine are built and tested, 36 ready-made asks ship with it, and the free plan gives 25 do-it-for-me runs a month with no account at all.
What does not exist yet is just as worth saying. There is no Chrome Web Store listing, so installing means loading it from the repository. Pro has a price on the pricing section and no checkout behind it — nothing on this site can charge you. And it has not yet met a large number of strangers' websites, which is the only real test a thing like this has.
The code is public. If you want to see how any of the above is actually implemented, or tell us where it broke, that is the place.