Site helpers

What it's for

Site helpers are the small automations that run inside a page: the ready-made ones Umbra ships for popular stores, and the helpers you write or record yourself. Turn one on and it does its job whenever you land on a matching page — tidying a checkout, logging what you bought, or whatever your own code does — so you're not repeating the same clicks in twenty Sessions by hand.

The screen has three views: Ready-made, Mine, What ran. Every helper is a switch you can see, and everything a helper does is written down where you can read it.

Always on

Three cards at the top have no switch, because they describe how every session behaves rather than an option you set:

Ready-made helpers

These are the automatic ones. Each card is a store — Ticketmaster, a specific retailer, Shopify — with the sites it covers under the name, and each switch on the card is one behaviour said in the outcome it produces, not the subsystem it belongs to: Tidies the checkout page, Logs what you buy. Flip a switch on and that helper runs by itself every time you visit that store, in every Account. There is nothing to trigger.

Two universal helpers show up across stores. Checkout hygiene ("Tidies the checkout page") clears the clutter a page throws at checkout so the fields you need are reachable. Purchase capture ("Logs what you buy") reads the confirmation page and files the order into your Ledger, with card numbers and emails stripped first.

What a helper will and won't do

A managed helper prepares a page. It does not buy on it.

There is one thing hygiene does touch on your behalf, and it's worth naming plainly rather than hiding behind "never touches anything for you."

Mine

Mine holds the helpers you write or record, as cards with the same switch the ready-made ones carry. Give a helper one or more URL patterns — one per line — and it runs automatically on any page that matches; leave the patterns blank and it's manual, run with the play button against the Session you have open. Where it runs on each card answers exactly that, pattern by pattern. Write a helper opens the editor; Import from a file reads a .js file into that editor for you to review and save — nothing is added behind your back. Every helper exposes a small umbra helper in the page: $, $$, fill, click, waitFor, sleep, log, notify, url.

To capture a helper instead of typing it, press Record my clicks. Recording is owned by the app, not by this screen — the Stop button lives in the app chrome and outlives the screen, because you have to leave this screen to reach the page you're recording. Deleting a helper is confirm-gated and can't be undone; a long recording is real work to lose.

Starters sit in a fold below your cards: ready-made scripts you insert and then tweak. Insert one and it lands in the cards above, yours to edit — reload-until-in-stock, queue alerts, captcha solving with your own key, and a capture-dump diagnostic for when a purchase lands in the Ledger wrong.

What ran

Whenever a helper runs, what it did lands in What ran — a table, newest first: which Session it ran in, when, what it did in the helper's own words, and whether it finished or failed. Umbra keeps the most recent 200 lines from this run of the app. It's the first place to look when a helper isn't doing what you expected, or when a capture landed an order in the wrong shape.

Code formats

The Code formats fold explains how Umbra reads verification codes out of a site's email or texts — a Ticketmaster pattern and a generic pattern are built in. To give one site its own inbox, number or pattern, go to Accounts → the Account → Sign-ins → Codes; this fold only lists the built-in presets and points there.