Self-evolving tools

Did something once and want it every time? Asyde can save a conversation as a reusable tool. You walk through the task once; Asyde distills it into a small, named recipe you can run again just by asking.

The important part: a recipe is data, not code. Asyde never writes a program to run in your browser. It records which of a fixed set of steps happened, in order — and a generic interpreter that ships inside the extension replays them.

Save a conversation as a tool

1. Do the task once in the panel — open a page, read it, maybe fill a field and submit.
2. Choose Save as tool. Asyde proposes a recipe: a name, a description, and the steps it saw.
3. Review it and save. From then on, ask for it by name and Asyde runs it.

What a recipe looks like

A recipe is a frozen list of steps over six primitives — read, scroll, media, page_fetch, click, and fill. Here’s one that files a weekly status update:

{
  "label": "Post weekly status",
  "description": "Open the team dashboard, filter to this week, and submit a status note.",
  "hostScope": "dashboard.example.com",
  "params": [{ "name": "note", "required": true }],
  "tierCache": "mutating",
  "steps": [
    { "primitive": "read", "args": {} },
    { "primitive": "fill", "args": { "label": "Status", "value": "{{note}}" } },
    { "primitive": "click", "args": { "text": "Submit" } }
  ]
}

No URLs to fetch behind your back, no free-form code — just named steps the interpreter knows how to run.

Two tiers: safe and mutating

Every recipe is classified by what its steps actually do. The classifier lives in shipped code and re-derives the tier from the frozen steps every time the tool runs — a tool can never quietly promote itself.

Safe — only reads: read, scroll, media, or a page_fetch that’s a GET. A safe tool runs on its own, no prompt. Nothing on the page changes.

Mutating — anything that changes the page: click, fill, or a non-GET request. A mutating tool asks for your approval once, when you save it. After that it can run, but you always saw and approved what it does.

Scoped to one site

A recipe is bound to the host you created it on. A tool you saved on your dashboard won’t fire on some other site, and its page requests are subject to the browser’s normal same-origin rules — which is also what lets it carry your existing login on that site, and only that site.

On your device, distillation is stateless

When you save a tool, the relevant conversation turns are sent once to distill them into the recipe, then returned to you — nothing is stored on Asyde’s servers. The recipe lives only in your browser’s local storage. Your extension assigns its identity and host scope, re-validates the shape, and keeps it on-device.

You can turn a tool off or delete it at any time from Settings. See Privacy & security for the full data flow, and Use cases for worked examples, from a safe saved search to a mutating multi-step routine.