Skip to content
aYOUne

Browser control by the Copilot

Browser control by the Copilot

The AI Copilot can carry out tasks in your browser for you: open a page, click something, fill in a form, read content or take a screenshot. The Companion runs these steps in your Chrome, using your own sign-in on the sites involved.

Turning it on

Browser control is off after installation. Turn it on in the Companion settings – under Features or under AI Copilot with Allow the Copilot to control this browser. Both switches are the same; switching it off ends a running session immediately.

What the Copilot can do

Open pages, go back and forward · click, type, press keys, select, scroll, drag · read and extract content · wait for elements · open, switch and close tabs · handle dialogs and cookie banners · download and upload files · take screenshots.

You stay in control

  • Approval per session. Before the Copilot opens a tab, a small window asks Darf der aYOUne-Copilot diesen Browser steuern? (May the aYOUne Copilot control this browser?) with Zulassen (Allow) and Ablehnen (Deny). Without an answer within one minute the request counts as denied and no tab opens.
  • Its own tab. The Copilot works in a new tab it opens itself – not in the tab you are using and not in your other tabs.
  • Visible notice. While the Copilot controls a tab, the tab shows aYOUne steuert diesen Tab (aYOUne is controlling this tab) with a Stoppen (Stop) button. One click ends the control immediately.
  • Automatic end. If no new command arrives for two minutes, control ends by itself.
  • Levels. Every step is checked before it runs and assigned to one of three levels: read, interact or submit. Submit covers, for example, clicking a submit button, pressing Enter in a form, typing into password or payment fields and uploading files. The Companion only carries out such a step if it has been explicitly approved for that website.
  • Asking you first. If a step needs your consent, you receive a notification in which you approve or reject it. Without your approval the step is not carried out.

Chrome's notice

For clicks and typing that a web page should treat as real user input, the Companion briefly attaches to the Copilot's tab. Chrome then shows its own notice at the top that the extension is accessing this browser ("started debugging this browser"). This is expected and disappears after the step.

Naming your browser

If you use the Companion in several browsers, give each one its own name under Settings → Account & organization → Name dieses Browsers (Fernsteuerung) (name of this browser; the field is currently labelled in German). The Copilot can then address exactly this browser. The name stays in this Chrome profile and is not synced to other devices.

Work with this page

Ready-made instructions for your AI tool. Copy, paste, go — the AI fetches the content itself via the address in the text.

Summarise the steps for me The essentials, in the right order.
Open in ChatGPT 
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/browser-control.md
The complete collection: https://ayoune.com/en/docs/companion.md

Summarise the content for me.

- First, in two sentences: what is this about?
- Then the steps in the order I need to take them.
- One line per step, in plain language.
- At the end: what I should have ready beforehand.

Leave out nothing I need in order to actually finish.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Explain what I need this for What it is good for — and when it is worth it.
Open in ChatGPT 
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/browser-control.md
The complete collection: https://ayoune.com/en/docs/companion.md

Explain to me what I need this for.

1. Which problem does it solve? In one sentence, from my point of view.
2. Three typical situations in which it genuinely helps me.
3. When I do NOT need it — that saves me time.
4. What I can do instead if it is not a fit.

Stick to what the source says. Where it gives nothing, say so openly instead
of guessing.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Help me set this up Step by step, asking me as you go.
Open in ChatGPT 
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/browser-control.md
The complete collection: https://ayoune.com/en/docs/companion.md

Walk me through the setup step by step.

- First tell me what I need to have ready (access, data, time).
- Then take me through ONE step at a time. Wait for my "next".
- For each step, say how I can tell that it worked.
- If something goes wrong, ask me for the exact message instead of guessing.

If the instructions leave a point open, tell me so rather than inventing it.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Help me with a problem Narrow down the cause instead of guessing.
Open in ChatGPT 
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/browser-control.md
The complete collection: https://ayoune.com/en/docs/companion.md

Help me narrow down a problem.

- First ask me what I observe and what I expected instead.
- From that, derive the most likely causes consistent with this source.
- For each cause, give me ONE test that confirms or rules it out.
- Order them so the cheapest test comes first.

Do not guess. If the source does not cover the problem, tell me where I should
look next.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
Explain it in plain words No jargon, from the ground up.
Open in ChatGPT 
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/browser-control.md
The complete collection: https://ayoune.com/en/docs/companion.md

Explain the content so that someone without prior knowledge understands it.

- Start with the purpose: why does this exist at all?
- Explain technical terms in half a sentence on first use.
- One everyday comparison where it genuinely holds — none where it limps.
- At the end: the three things worth remembering.

Do not shorten by dropping conditions. A simplification that hides a
prerequisite is a false statement.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.
A checklist to tick off To follow along while you do it.
Open in ChatGPT 
Read the following documentation by tolinax UG and work with it.

This page: https://ayoune.com/en/docs/companion/browser-control.md
The complete collection: https://ayoune.com/en/docs/companion.md

Turn this into a **tick-off checklist** for practical use.

- Exactly one action per item, in the imperative.
- Order it so that no item depends on a later prerequisite.
- Prerequisites and pitfalls as indented sub-items.
- End with an acceptance step: how do I know everything is right?
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
  instead of this snapshot. If not, ignore this point.

Was this article helpful?

👎 No (0)
Leave a comment