Use cases

The same panel, from a glance to a workflow.

Every story below happens in the quiet side panel, on the page you're already on. They run simple to involved — the last two you teach once and reuse.

  1. 01

    Monday, a long read

    Summarize this article before the meeting

    1. 1.Open the article and click the Asyde launcher.
    2. 2.Tap “Summarize”, or ask for “just the three decisions and who owns them”.
    3. 3.Read the short version in the panel; copy it into your notes.
    Safe · runs on its ownShrink the long stuffPull out what matters
  2. 02

    Inbox, before coffee

    Reply to this email in my voice

    1. 1.Open the Gmail thread. Asyde reads the open thread, not your whole inbox.
    2. 2.Tell it the gist: “yes to Thursday, and I’ll bring the growth numbers.”
    3. 3.Get a draft that sounds like you. Insert it into the reply box, or copy it.
    Safe · runs on its ownReply in your voiceRight where you work
  3. 03

    A sign-up you’d rather skip

    Fill this form — I’ll review before it sends

    1. 1.Save your details once in Settings (kept on your device).
    2. 2.On the sign-up, ask Asyde to fill it in.
    3. 3.It fills every field except passwords and shows you the result to review.
    4. 4.You submit — nothing is sent until you say so.
    Mutating · asks onceFill forms in a clickNever touches a password field
  4. 04

    A bug lands in your lap

    File this as a GitHub issue and ping the team

    1. 1.Connect GitHub as an MCP server once, and add your team’s notify webhook as an HTTP tool.
    2. 2.On the bug report, ask: “file this as a GitHub issue and post it to #eng.”
    3. 3.Asyde calls both tools from your browser and links you the new issue.
    Add your own toolsMCP + HTTPBuilt-in browser toolsConnecting tools
  5. 05

    A search you run every day

    Save a site search as a reusable tool

    1. 1.Walk Asyde through it once: open the site, run the search, read the top results.
    2. 2.Choose “Save as tool”. Asyde distills the steps into a small, named recipe.
    3. 3.Because it only reads, it’s a SAFE tool — next time, just ask by name and it runs.
    Safe · runs on its ownTurn a chat into a toolRuns on your deviceSelf-evolving tools
  6. 06

    A weekly ritual, in one step

    Teach Asyde a multi-step task, approve it once

    1. 1.Do the flow once: open the dashboard, filter to this week, fill the status field, submit.
    2. 2.Save it as a tool. Asyde captures the steps as data — never code it wrote itself.
    3. 3.Because it types and clicks, it’s a MUTATING tool: it asks for your approval once, when you save it.
    4. 4.From then on, one ask replays the whole routine — and you can delete the tool anytime.
    Mutating · asks onceTurn a chat into a toolOne approvalEverything on your deviceHow self-evolving tools work

Try it on this page.

The Asyde launcher in the corner reads this very page. Or install it and bring it to the page you actually work on.