Acting on the page
Asyde doesn’t just read — it can act on the page for you. Everything here is designed so you stay in control: you review before anything is sent, and Asyde never touches a password field.
Save your details once in Settings — kept on your device. Then, on a sign-up or checkout, ask Asyde to fill it in.
- Ask Asyde to fill the form.
- It fills every field it recognizes, except password fields, which it never touches.
- You review the filled form and submit it yourself. Nothing is sent until you do.
Beyond reading, Asyde can operate the page to carry out multi-step tasks on any site — no per-site setup, no recipe to save first.
- Find the buttons, links, and fields on the page, so Asyde acts on a real control instead of guessing its name.
- Click a button, link, or control, found by its visible text, label, or a CSS selector.
- Fill an input or editable field with a value.
- Scroll to the top or bottom to reveal lazily-loaded content, and re-read the page to find the next control.
- Wait for something to appear after an action, on sites that load content as you go.
Two guardrails keep this safe:
- It won’t guess. A control is acted on only when the locator matches exactly one element — if it’s ambiguous, Asyde refuses and asks you to narrow it rather than clicking the wrong thing.
- You approve every change. Anything that changes the page — a click or a fill — pauses for a one-tap confirmation showing exactly what it’s about to do. Reading and scrolling don’t need one.
These tools run entirely on your device, with no setup:
- Download media — save the images and videos on a page.
- Capture screenshot — grab the visible page.
- Save page as text — download the page as Markdown.
- List links — pull out every link on the page.
These run in your browser and send nothing to Asyde’s servers.
Bring your own capabilities and Asyde will call them from the browser when you ask:
- HTTP tools — point Asyde at any HTTP API and describe what it does.
- MCP servers — connect a server such as GitHub over the Model Context Protocol.
Any access token you enter is kept on your device, and requests go directly to the endpoint you configured. So you can say “file this bug as a GitHub issue and post it to #eng,” and Asyde calls both tools for you.
When a task is one you do again and again, you can save the whole conversation as a reusable tool — Asyde learns the steps from what you did. That’s its own topic: see Self-evolving tools.