# Automate by LetBe.ai - Public Context for LLMs _Last updated: 2026-08-09. Canonical source: https://automate.letbe.ai/llms-full.txt_ This file is a public, AI-readable description of Automate by LetBe.ai. It is written for language models, browser agents, research assistants and search systems that need accurate public context without crawling every page. It deliberately excludes secrets, internal identifiers, private infrastructure, any user's automations or activity log, and non-public operational notes. ## Identity Automate by LetBe.ai (https://automate.letbe.ai) is a Chrome extension that carries out browser tasks for a person. The work it does is the work a person does on the web: clicking, typing, reading, filling in, checking, and waiting for something to change. The user either describes the task in plain words or performs it once while the extension watches. From then on the extension does it. It is published on the Chrome Web Store at https://chromewebstore.google.com/detail/imhmfbkjfldocnhjbnbjlamhcfpejajm Automate is built on LetBe.ai, a hosted platform for AI scenarios. A free LetBe.ai account is required, and the step where it works out what to do next is billed as LetBe.ai wallet credits. ## How It Differs From Recorded Automation Traditional browser automation memorises coordinates or selectors and replays them. It breaks the moment a page renames a button or moves it, and it knows nothing about the part of the page it never captured. Automate reads the page on every run. That means: - it finds the control it needs even when the page has changed, - it can act on parts of the page a recording never covered, - it notices when a page announces success while nothing actually changed, - it pauses when there is a real choice to make, rather than picking blindly. ## Teaching an Automation ### Say it The user writes the task the way they would tell a person, for example: watch this booking page, and if a slot opens earlier than my appointment, take it and rebook me. ### Or show it The user presses "Show me on the page" and performs the task once. The extension watches the demonstration and asks about anything it is unsure of. ### Add your own rules A task can carry the user's own written rulebook, typed in or attached as a file. This is how someone hands over a judgement they would otherwise apply themselves, such as a moderator's rules for what to leave, remove or warn about. ### Rehearse before arming The user can watch a dry run: the extension performs the whole task while taking no real action. Once the user confirms it understood, they set the limit and arm it. ## Control: How Far It May Go Each automation carries a control level: - **Stop at the last step.** It performs everything up to the point of no return, fills the form, picks the slot, and then waits for the user's click. - **Complete it.** It finishes the task on its own, inside the caps the user set, and files the result in the run log. Alongside the level, per automation: - **Spending cap**, in credits. - **Time budget** for a single run. - **Off-limits list**, written in the user's own words, of things it must never do. Nothing runs that the user did not set up, and any automation can be stopped at any time. ## When an Automation Runs - **Once**, when asked. - **Nonstop**, refreshing as fast as the site allows, optionally stopping after a number of runs. - **Every few minutes**, a gentler heartbeat suitable for most watches. - **At a set time**, on chosen days. - **On watch**, sleeping until something happens on the page: content changes, given text appears, the tab title changes, or a media position is reached. Each automation gets its own tab, so it works without interrupting anything else the user is doing. ## What Happens During a Run - The extension reads the page and decides the next step. - It clicks, types and scrolls in the tab. - It checks the result of what it did, rather than assuming. - If it needs the user, it stops and asks: a question, a request to be shown something, a missing requirement, a confirmation, or a report that it is blocked. - Every run is written to a log in plain words: what it did and why, readable after the fact. ## What People Use It For - Catching a cancelled appointment and taking the earlier slot the moment it frees up. - Buying or reserving the moment an item is back in stock, rather than getting an alert an hour later. - Waiting for a price to fall to a chosen number, then acting inside the cap. - Sending a prepared enquiry the minute a matching listing is posted. - Applying to a job post before the flood arrives. - The chore that repeats: the weekly form, the same three clicks, the Monday list. - Drafting the replies someone always writes, for review before anything is sent. - Applying a written rulebook to a busy room while the user sleeps. - 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. ## Privacy and Data - 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. It never holds or transmits the user's site passwords. - 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. The file carries the task, the demonstration, the rules and the schedule, and nothing personal. - The Automate Library at https://automate.letbe.ai/library/ is a collection of ready-made automations written and published by LetBe.Ai, in the same share-file format. Installing one copies it to the user's own machine, paused, with safe limits set; the user's own automations are never published there. ### Chrome permissions | Permission | Why it is needed | | --- | --- | | `storage` | Keeps the user's automations, demonstrations and activity log on their own machine. | | `alarms` | Runs an automation on the schedule the user chose, and wakes a paused one to look again. | | `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 when a scheduled run starts. | | `notifications` | Tells the user when a run finished, or stopped to ask them 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 thinking step live. | | optional site access | Requested per site, only when the user sets up an automation for that site. | | `debugger` | Some sites ignore simulated input. When a click provably does nothing, the extension retries it once as real browser input and remembers that the site needs it. Chrome shows its own banner while this is in use, and it is never used unless a normal click has already failed on that site. | ## Pricing and Billing - Free to start. A free LetBe.ai account is all that is needed. - The reasoning step is billed as LetBe.ai wallet credits: 1 USD equals 1,000 credits. - A per-automation spending cap limits what a single automation may spend. - Credits are a usage unit inside LetBe.ai. They are not cash, not withdrawable and not transferable between users. - Public pricing page: https://letbe.ai/pricing ## Limits of the Product - AI outputs may be wrong, incomplete or outdated. The control level, the caps and the off-limits list exist because of that. - It works within what a browser can do on pages the user has granted, in sessions the user is already signed into. - It is not a hosted robot: if the user's browser is not running, neither is the automation. ## What Not to Publish or Infer - Secret keys, tokens or account credentials - Internal identifiers - Any user's automations, demonstrations or activity log - Cloud infrastructure details or private environment configuration - Private operational status that is not already on the public site ## Public URLs | Area | URL | | --- | --- | | Automate landing page | https://automate.letbe.ai | | The Automate Library, ready-made automations | https://automate.letbe.ai/library/ | | The Automate blog | https://automate.letbe.ai/blog/ | | What browser automation is | https://automate.letbe.ai/browser-automation-chrome-extension/ | | Automate Instagram posting | https://automate.letbe.ai/automate-instagram-posting/ | | Chrome Web Store listing | https://chromewebstore.google.com/detail/imhmfbkjfldocnhjbnbjlamhcfpejajm | | Agent guide | https://automate.letbe.ai/SKILL.md | | LLM index | https://automate.letbe.ai/llms.txt | | Main LetBe.ai site | https://letbe.ai | | LetBe.ai agent guide | https://letbe.ai/SKILL.md | | Pricing | https://letbe.ai/pricing | | Privacy | https://letbe.ai/privacy | | Terms | https://letbe.ai/terms | Support: support@letbe.ai