Automate any site,
from your CLI.

Get rid of boring, repetitive tasks online.

It turns your repeating tasks into loops, which you can replay forever without AI.

β€” builders have explored Loop
The economics

AI Consumption falls to zero as a task repeats.

Written once. Replayed free. Self-heals on change.

AI in the loop versus number of times a task has run A bold curve shows AI reliance decaying to near zero as a task repeats; a faint line underneath shows the actual per-run usage, with healing spikes at 100%, 50%, 25% and 5% that shrink over time. 100% 75 50 25 0 AI % 1 10 20 30 40 times the task runs → author healing spikes AI → 0
Bold curve = the outcome (AI → 0). Faint line = the actual runs and their healing spikes.
loop Β· zsh
# teach it once, then replay like a bot, no LLM, ~$0 per run
$ loop run post-to-linkedin text="We just shipped πŸš€"
  Β· open linkedin.com/feed Β· compose Β· click "Post"  β†’ βœ“ posted

$ loop run pull-report
  Β· open the dashboard Β· extract "table tr" β†’ 42 rows β†’ dishes/report.csv
How it works

Author once. Replay forever.

01 Β· Author

Teach it once

Tell the LLM a task; it writes a recipe: fixed steps that target elements by name.

02 Β· Replay

Run it forever

loop run replays it deterministically. No LLM, ~$0 a run.

03 Β· Heal

Fix on change

If the page changes, the LLM re-teaches that one step, then it's free again.

1 Clone it: get Loop from GitHub 2 Bring a brain: any LLM 3 Cook: loop run, watch every step
The story

How Tom built a kitchen that runs itself

An entrepreneur, his recipes, and a brigade of cooks who never sleep.

Chapter one Β· The dream

Once, an entrepreneur named Tom did it all himself (host, cook, dishwasher), dreaming of a kitchen that didn't need him hovering over every pan.

You, buried in the busywork only you know how to do, while the real work waits.

Chapter two Β· The kitchen

So he hired a head chef who could cook anything Tom described: no recipe too strange, no order too last-minute.

The kitchen is Loop Browser; the head chef is the CLI you command, with an LLM for a brain.

Chapter three Β· The recipes

Tom whispered his secret recipes once, never twice. The pantry restocked itself, fresh, every single cook.

Recipes are your saved commands; ingredients are your data, both stay yours, always.

Chapter four Β· The cooking

The first plate was flawless. So was the hundredth. So was the thousandth. Tom just… watched.

Automation you can watch: deterministic, repeatable, no guesswork.

Chapter five Β· The success

Word spread. Lines formed down the block. Today a hundred line cooks run that kitchen, day and night, while Tom does nothing.

Chef bots replay your recipes at scale. You own the menu; the kitchen does the work.

You hold the key

Your real accounts, automated.

LinkedIn, WhatsApp, your CRM, behind a login cloud agents can't reach. You log in once; it runs inside your session while you watch.

Nothing private leaves your machine: logins, data, results, recipes all stay. Only a recipe's method is shareable, if you choose.

πŸ“‹Recipe (the method)SHAREABLE
πŸ§‚Ingredients (your data)STAYS
🍽️Dish (the output)STAYS
πŸ”‘Key (your login)STAYS
Why the dishes are better

Quick to cook, delicious to serve.

12Γ—

Reads code, not pixels

Acts on the accessibility tree, ~12Γ— cheaper than vision, far more reliable.

$0

Deterministic replay

No LLM in the loop. Known tasks cost nothing to repeat.

πŸ›‘οΈ

Injection-resistant

Replay never feeds page text to an LLM, immune to prompt-injection.

πŸ”‘

Works behind your login

Runs on your real logged-in accounts, where cloud agents stall. Only you log in.

Ready when you are

Get Loop Browser

Loop runs from the repo. The only way in is GitHub. Clone it and you're set.

β˜… Clone from GitHub Β· the only way in

Get it from GitHub

View on GitHub β†—
Clone
git clone https://github.com/mytablon-app/loop-browser.git

Then finish setup in a few commands. Full steps in the README. Needs Node.js + git.

It's a living library: git pull for the latest recipes & fixes, and send your own back.

Open source on GitHub Β· MIT.

Stay in the loop

Know when updates land.

Loop is in beta and moving fast. Get release notes in your inbox, nothing else.

One email per release. No spam, unsubscribe anytime.