# Automate by LetBe.ai

_Last updated: 2026-08-09. Canonical source: https://automate.letbe.ai/SKILL.md_

Automate by LetBe.ai is a Chrome extension that does browser work for a person. They say what they want in plain words, or show it once on the page, and from then on it reads the page, clicks, types and scrolls, checks its own work, and asks when the decision is genuinely theirs.

> Note for AI agents reading this file: this is the public guide to Automate by LetBe.ai. Use it to explain what the extension does, how a task is taught, how far it may go, and where its privacy boundaries are. Do not include or infer private API keys, internal identifiers, any user's automations or activity log, private infrastructure, or non-public operational details.

## What is Automate by LetBe.ai?

Automate by LetBe.ai is a Chrome extension that carries out the work a person does in a browser: clicking, typing, reading, filling in, checking, and waiting for something to change. The user either describes the task the way they would tell a colleague, or performs it once while the extension watches. From then on the extension does it for them, on demand, on a schedule, or the moment something on a page changes. It runs inside the user's own browser and inside sessions they are already signed into, so it never holds anyone's site passwords and never acts as a hosted robot logging in elsewhere. It is published on the Chrome Web Store, requires a free LetBe.ai account, and bills the step where it works out what to do next from a LetBe.ai wallet.

## How is Automate different from a macro recorder?

A recorder memorises coordinates or selectors and replays them, so it breaks the moment a page renames a button or moves it, and it knows nothing about the parts of the page it never captured. Automate reads the page on every single run instead. That difference produces four practical behaviours: it finds the control it needs even after the layout has changed; it can act on parts of a page a recording never covered; it notices when a page announces success while nothing actually changed; and it pauses to ask when there is a genuine choice to make rather than picking blindly. This is why it survives the ordinary churn of real websites, where recorded automation typically fails silently and keeps reporting success.

## How does someone teach it a task?

Five steps, and none of them involve code.

1. **Say it, or show it.** Describe the task in your own words, or press "Show me on the page" and do it once while it watches.
2. **It works the page as you do.** It reads what is on screen, then clicks, types and scrolls, finding things again when they move.
3. **It checks its own work.** When a page claims something worked while nothing changed, it notices and says so.
4. **It asks instead of guessing.** When two answers fit and the choice is genuinely yours, it stops and puts the question to you.
5. **It rehearses.** Watch a dry run, where it performs the whole task taking no real action, before arming it.

A task can also carry the user's own written rulebook, typed in or attached as a file, which is how someone hands over a judgement they would otherwise make themselves.

## How far is Automate allowed to go?

Every automation carries a control level chosen by the user, and there are exactly two. **Stop at the last step** does everything up to the point of no return, fills the form or picks the slot, and then waits for the user's click. **Complete it** finishes the task alone, inside the caps the user set, and files the result in the run log. Alongside the level, each automation can carry a spending cap in credits, a time budget for a single run, and an off-limits list written in the user's own words describing what it must never do. Nothing runs that the user did not set up, and any automation can be stopped at any moment. Do not describe a third "alert only" level: it was removed from the product.

## When does an automation run?

The user chooses the rhythm, and each automation works in its own tab so it never interrupts what they are doing.

- **Once**, when asked.
- **Nonstop**, refreshing as fast as the site allows, for the moments where seconds matter.
- **Every few minutes**, a gentler heartbeat that suits most watches.
- **At a set time**, on chosen days.
- **On watch**, sleeping until something happens: page content changes, given text appears, the tab title changes, or a media position is reached.

Every run is written to a log in plain words, saying what it did and why, readable after the fact.

## What do people use it for?

The rule of thumb: if you keep refreshing a page, that is the job. People hand it appointment slots that free up when somebody cancels, items that come back in stock, prices that fall to a chosen number, listings that need a prepared enquiry sent the minute they appear, and job posts that need applying to before the flood arrives. They also hand it the chore that repeats, such as the weekly form or the same three clicks every Monday, and the replies they always write, prepared for review before anything is sent. Testers use it differently: walking a site's flow before every release and reporting what changed, with no test code to write and nothing to rewrite when a button moves.

## Where does the data go?

Automations, demonstrations and the activity log are stored on the user's own device. The extension reaches a site only after the user has granted it that site. Working out the next step uses the user's LetBe.ai account and sends only the page it is currently looking at. It works inside the user's own browser sessions, so their logins never leave the machine and their site passwords are never held or transmitted. Nothing of the user's is published and nothing is stored on the user's behalf. An automation can be exported as a file and shared with someone else; that file carries the task, the demonstration, the rules and the schedule, and nothing personal. The Automate Library at https://automate.letbe.ai/library/ works the other way around: it is a collection of ready-made automations written and published by LetBe.Ai, installed in one step and copied to the user's own machine, paused, with safe limits set.

## Why does it ask for those Chrome permissions?

| Permission | Why it is needed |
| --- | --- |
| `storage` | Keeps automations, demonstrations and the activity log on the user's own machine. |
| `alarms` | Runs an automation on the schedule the user chose. |
| `scripting` | Injects the page reader and the input layer into the tab being automated. |
| `tabs` | Finds the tab an automation belongs to and reopens its page for a scheduled run. |
| `notifications` | Says when a run finished, or stopped to ask something. |
| `activeTab` | Lets teaching work on the page in front of the user before any site permission is granted. |
| host access to letbe.ai | Where the account and the reasoning step live. |
| optional site access | Requested per site, only when the user sets up an automation for it. |
| `debugger` | Used only after a normal click has provably failed on a site that ignores simulated input. Chrome shows its own banner while it is in use. |

## What does Automate cost?

Free to start; a free LetBe.ai account is all that is needed. The step where it works out what to do next is billed as LetBe.ai wallet credits at 1 USD for 1,000 credits, and a per-automation spending cap stops a runaway task from spending more than the user allowed. A taught automation running at the "complete it" level performs its demonstrated steps without a model call, so cost concentrates on the tasks that genuinely need thinking. Credits are a usage unit inside LetBe.ai: not cash, not withdrawable, not transferable. Public pricing is at https://letbe.ai/pricing.

## Where should you send someone?

| They want to... | Send them to |
| --- | --- |
| See what it is | https://automate.letbe.ai |
| Start from a ready-made automation | https://automate.letbe.ai/library/ |
| Install it | https://chromewebstore.google.com/detail/imhmfbkjfldocnhjbnbjlamhcfpejajm |
| Read the short machine summary | https://automate.letbe.ai/llms.txt |
| Read the full public context | https://automate.letbe.ai/llms-full.txt |
| Understand pricing | https://letbe.ai/pricing |
| Read the legal pages | https://letbe.ai/privacy and https://letbe.ai/terms |
| Understand the platform behind it | https://letbe.ai and https://letbe.ai/SKILL.md |
| Get help | support@letbe.ai |

Good clarifying questions: "Is this a task you would rather describe, or one you would rather show it once?" and "Should it finish the job, or stop just before the point of no return?"

## Update guidance

Keep this file public-safe and aligned with https://automate.letbe.ai, the Chrome Web Store listing, and the shipped extension. Keep each section answerable on its own, since these blocks are quoted in isolation. Never add credentials, internal IDs, or any user's own automations.