Skip to content

Releases

Storm 0.3.0

Choose a tag to compare

@trayanm trayanm released this 16 Nov 12:43
1ac5ca5

Storm 0.3.0 makes recipes, the way Storm reads a website's list without an LLM, something you can write, check and fix yourself, and lets them read more kinds of sites. Nothing leaves the system without Act, as before.

What's new

  • A guide to recipes: docs/recipes.md. When to use one, teaching and writing it, a walkthrough, every key, what to do when a site changes, and a troubleshooting table.
  • Edit a recipe on its page. Each version shows as YAML. Edit (or Edit from here on an older one) saves your change as the next version, checked like an import; Download saves a version as a file. Teach again starts from the recipe.
  • Try a recipe before a pipeline uses it. Try reads the list with the params you give and shows the items in a table, or what didn't match with a screenshot of the page. It changes nothing: the recipe isn't marked working or broken, and nobody is told. Dry runs of browser.extract now leave the recipe alone too.
  • "Load more" buttons and endless lists. Besides a next link and page numbers in the address, a recipe can press a "Load more" button (next: { kind: more, selector: … }) or scroll to the bottom (next: { kind: scroll }).
  • Detail pages. A recipe's detail section names fields to read on each item's own page (a job ad's description, a listing's floor). The new step browser.details opens them after data.dedupe, so only new items are opened, at the recipe's pace and on its site only.
  • Params explained where you use them. The Teach form asks for the Search results page and shows the address the recipe will keep as you type (https://www.bergfreunde.eu/s/<query>); Try shows the address it will open.
  • pnpm dev on Windows no longer fails with EPERM while the watchers start.

Upgrading from 0.2.0

git pull and ./docker/storm up. There are no new migrations or settings.

Requirements

Unchanged: Docker with Compose v2 and a Claude API key. Single user, AGPL-3.0.

Full list of changes: v0.2.0...v0.3.0

Storm 0.2.0

Choose a tag to compare

@trayanm trayanm released this 15 Nov 14:47
0ffcdbf

Storm 0.2.0 makes it usable from your phone, with more than one account, and with files. Nothing leaves the system without Act, as before.

What's new

  • Telegram commands start pipelines. /task Buy milk, /memo …, or a receipt's photo captioned /paper Washing machine add to an App. Any pipeline can have its own command; Settings → Telegram commands lists them all, with the pipeline each one starts, and which are off.
  • Several email and Google accounts. Email accounts move from .env to Settings → Email accounts, several, one the default, each password sealed like a credential. Google accounts are connected in Settings too; calendar steps and topics' Drive folders choose one. An email waiting for Act, in the Inbox and on Telegram, says which account it goes From.
  • You choose what a pipeline uses. Pipelines and Apps name slots (a credential, an email or Google account, a setting) and you fill them on a What it needs card, once per pipeline or per App. Credentials are chosen by id, never by name: renaming one breaks nothing.
  • Files and images in Apps. Forms take files and images (checked by content, thumbnails in lists). Pipelines keep an email's attachment, a download or a Telegram photo with file.keep, and read it back with file.read or llm.extract.
  • Four new example Apps, sixteen in all: Tasks (by due date, with a morning list), Memos (with a photo), Papers (receipts and warranties read from their photo or PDF, a warranty's end in the calendar) and Monitors in Server ops (http.check and net.check every five minutes, response times, certificate expiry, an incident when one goes down).
  • Finding your way with many pipelines. The pipelines list is grouped by App, with a search. An App says which of its pipelines are off and what that means, and the menu marks an App none of whose pipelines runs on its own.
  • Topics read the mailboxes you choose, and a GitHub source keeps its token by id.
  • Clearer errors. A step whose input doesn't fit says which field and the reference it came from, instead of the validator's JSON.

Upgrading from 0.1.0

  1. Create the App files folder before starting: mkdir -p data/documents/app-files (or under your STORM_DATA_DIR), owned by uid 1000. ./docker/storm up stops and prints the command if it's missing.
  2. Add your mailbox again. The mail credential and the MAIL_*, IMAP_* and SMTP_* keys in .env are no longer used: add the mailbox under Settings → Email accounts (for Gmail, the same app password), then delete the old keys and, on the Credentials page, the mail credential.
  3. Connect Google again under Settings → Google accounts → Connect Google: the single connection of 0.1.0 is not carried over.
  4. Pipelines that used a credential by name show it on their What it needs card; fill any that waits for you.

Then git pull and ./docker/storm up. The migrations run by themselves.

Requirements

Unchanged: Docker with Compose v2 and a Claude API key. Single user, AGPL-3.0.

Full list of changes: v0.1.0...v0.2.0

Storm 0.1.0

Choose a tag to compare

@trayanm trayanm released this 13 Nov 14:19
75eebff

The first release of RealEntity Storm: your own automation agent, on your own server. Tell it in a chat what you want taken care of; it builds the pipelines, the data they keep and the pages where you follow it. Nothing leaves the system until you have seen exactly what will be sent and pressed Act.

What's in it

  • Apps, built from a sentence. "I'm looking for a job" or "keep my bills" becomes a typed, versioned App: data types, stages, list and detail pages, and the pipelines that fill them, proposed as one change for you to review.
  • Twelve ready-made Apps under Apps → Examples: Job Search, Bills, Prices, Releases, Tables, Trips, Clients, Apartments, Orders, Subscriptions, Car and Server ops.
  • A job search, end to end. Job boards read with recipes you teach once, postings scored against your profile and calibrated on what came of past applications, application forms filled and shown field by field before Act, follow-ups and interview invitations tracked from your email.
  • Over 40 step types: mail, browser (a real Chromium you can watch and take over), HTTP and RSS, LLM, data, database, calendar, documents, Telegram, timers and approval gates. The LLM combines steps; it can't add new ones or write code.
  • Topics: facts about your projects and customers, proposed from email, GitHub repositories and Google Drive folders, kept only once you approve them, and used in drafted replies.
  • It learns from you: approved texts become examples, edits become suggested rules, and a nightly reflection proposes pipeline changes.
  • Safety by design: a gate before every side effect, untrusted input treated as data, credentials encrypted and never shown to the LLM, allowed domains, rate limits, a monthly LLM budget and a kill switch.

Requirements

Docker with Compose v2 and a Claude API key. An OpenAI key (embeddings), an IMAP/SMTP mailbox, a Telegram bot and Google Calendar/Drive are optional. Local models are not supported.

Getting started

Follow Setup in the README; docs/self-hosting.md covers running it on a server, and docs/capabilities.md lists everything it can do.

Single user, AGPL-3.0.