A no-code Chrome automation extension can mean a reload timer, a local step graph that keeps running on one tab, or a cloud AI agent. Tab Automation is the middle one: Add Step, Pick on page, and Repeat, stored in chrome.storage.local, while Chrome is open.
Match the job, not the category label. The phrase is shared by products that do not do the same work.
Three products share this phrase
Reload timers keep one open page current. You set a wait. The tab reloads. You read the page yourself. Chrome has no built-in repeating reload; that job is how to auto refresh a tab in Chrome.
Local repeating graphs add steps on that same tab: click, type, wait, check text, walk matching links, send an alert. The graph runs again after Repeat. You pick the elements. Nothing leaves this computer except a webhook you chose.
Cloud or AI agents ask you to describe a task, adapt when a layout changes, export to a spreadsheet, or keep running after you quit the browser. Tab Automation does not do those jobs. If a sentence needs one of them to sound complete, it does not belong on this page.
Pick the column that matches the tab you leave open. A timer is enough when you only need a fresh dashboard. A graph is enough when the same tab must click, check, or walk links after you walk away. An agent is the right search when the work is “figure it out on any site” or “run it from the cloud.”
What no code means here
No code means you do not write a script. You open the side panel, click New Automation, pick the open tab, and add steps from a menu.
Pick on page writes a CSS selector for the control you click. The eye button highlights the match. You can choose Which match to use when the selector hits more than one node.
That is not natural language. There is no model that guesses the important element. A changed selector fails the step. There is no healer that rewrites it when the site ships a new layout.
Add Step is manual. There is no recorder and no “replay my clicks.” The steps reference lists every item with the same names you see in the panel.
What keeps running
Repeat is the End block. It cycles the whole graph on the assigned tab. It never reloads by itself. A new automation starts with Repeat on and a 30-second Fixed wait. You can choose No wait, Fixed, or Random range, stop after a cycle count, or Stop after a duration.
That loop is the difference between a run-once task and an automation you leave open. A timer is Refresh Page plus Repeat. A repeating click is Click Element plus Repeat. A listing walk is For Each Link on Page. A watch for a phrase is auto refresh until text appears.
One automation stays on one assigned tabId. Two tabs means two automations. The graph does not orchestrate a window.
Alarms fire while Chrome is open. They do not fire after you quit. Running automations are rescheduled when Chrome starts again. There is no clock-time start and no “run this at 9:00.”
What stays on this computer
Tab Automation does not create an account. Automations, Values, and webhook destinations live in chrome.storage.local on this computer. The extension does not send tab or page content to Tab Automation servers.
Output is local too: a value stored on the graph, a webhook Chrome POSTs from this machine, or a PNG under Downloads. There is no Sheets, CSV, or CRM export step.
Read the privacy policy for permissions. The Launch License is the current way to open every Add Step item and every Workflow during early launch. It is not a claim that a later paid version is for sale today.
When to pick something else
Choose a different tool when the job is larger than a tab you leave open:
- You need the run to continue after you quit Chrome.
- You want to describe a task in plain language, or you need the flow to adapt when the layout changes.
- You need a spreadsheet or CRM export, email or SMS, or a Zapier-class connection to other apps.
- You need one automation to drive several sites or several tabs together.
- You want to record a macro instead of adding steps.
Those are real jobs. They are not what this side panel ships. A local graph is the better fit when you already know the button, the field, or the phrase, and you want the same steps to keep running on that tab.
What we learned shipping a graph that loops
We built Tab Automation because a reload timer is easy to find and a looping graph is the product. People search for auto refresh. The useful work is often “reload, then look, then click or notify,” on a page that stays open.
Pick on page is slower than a prompt and more honest. You see the selector. You see the step fail in Activity when the node is gone. That is the tradeoff for staying deterministic and local.
The locked line on the homepage is the same idea: automations for the tabs you leave open. Auto refresh is the example that makes the extension findable. Repeat is what keeps the rest of the graph in motion.
If you already know the job, start with the matching guide. If you are still choosing a category, stay on this page until the three columns are clear, then leave.