The browser extension
Metis working inside the pages you already have open — authority portals, your ERP and forms — with action previews and approval controls.
On this page
Most aviation work does not happen in one system. You have an authority portal, a maintenance system, a supplier's website, a shared drive — and Avioverse. The extension is Metis reaching into those other systems, in the tab you already have open, in your own logged-in session.
It is the same assistant, not a second one. Same memory of you, same library, same rules.
What it is good at
Filling in what you already hold. You have the data in Avioverse; the portal wants it typed into thirty fields. Metis reads the form, maps your records onto it, fills it, and stops in front of the submit button.
Getting data back out. A portal that shows a table and offers no export. Metis reads what is on screen and brings it into your work.
Carrying a value between two tabs. Read a serial number from one system, enter it in another, without it passing through your short-term memory.
Working a page you have to interact with to see. Filters, site search, pagination.
What it can actually do
Three abilities, and it is worth knowing where the edges are:
- See — a map of what is on the page: text, headings, form fields and their current values, and your open tabs.
- Act — click, type, fill, select, scroll, wait, navigate. And submit, which is the special one, below.
- Run a small script — for a page that will not yield to ordinary reading. This one is not always available: many corporate sites carry a security policy that forbids running code, and on those pages Metis tells you plainly that the page's policy blocks it and continues with reading and clicking instead. Nothing silently fails.
The rules it works under
This is the part to read carefully, because the extension is the capability with the most reach and therefore the most restraint built into it.
Designated actions require approval. Explicit submissions, form-fill operations, clicks recognised as committing actions (such as save or delete), and scripts pause for a preview and approval. You cannot grant standing approval for these actions. Check the target and contents: website behaviour can make an ordinary interaction consequential too, and approval does not verify the result.
Credential filters reduce exposure. Page-reading filters exclude password fields and recognised credential patterns before results leave the page. These filters do not establish that every sensitive value has been recognised. Review what is on the page and avoid sharing confidential material without authority.
Scripts are filtered and approval-gated. Server-side checks reject recognised network, credential-access and dynamic-code patterns. This is a limited filter, not a guarantee of what a script will do. The full script is shown for separate approval before it runs; decline if you cannot establish its intended effect.
A new tab needs your say-so. The first time it wants to work in a different tab, you get a one-time card naming that tab's site. Decline, and that tab is never touched.
Page content is marked as untrusted. Metis is instructed to analyse it without following embedded commands. This reduces the risk of malicious instructions but cannot guarantee they will never affect a response. See Approvals, undo and your data.
How it feels to use
Open the side panel, say what you want in plain language, and watch the step log fill in: each thing it read, each thing it did, each approval it is waiting on. Nothing happens off-screen. There is a Stop button, and it stops.
Enter sends your message; Shift+Enter starts a new line. Each reply has its own copy button. It shows whichever name you have given the assistant, not a fixed one.
Where it differs from the rest of Metis
Two differences are worth knowing, because they are deliberate:
- It does not carry your full memory into every message. The chat in the app loads your profile and working rules on every turn; the extension does not, to keep it quick and to keep your personal context out of a third-party page's reach. It can still look things up in your memory when the task calls for it.
- It works alone. It does not delegate to helpers the way the full chat can for large parallel jobs.
Everything else — the library, your records, the named methods on a paid plan, the metering — is the same.
There is also a plainer distinction worth keeping straight. The extension acts in your browser, in your logged-in sessions, on pages you are looking at. Metis can also open an anonymous browser on the public web, which is a different capability with different limits — that one never logs in and never submits anything at all. See The modules it can reach.
Getting it
The extension is a Chromium add-on — Chrome, Edge, Brave and the rest of the family. It signs in with your ordinary Avioverse session: sign in to the web app first, and the side panel picks it up.
Informational only — you verify against the approved exposition before you act.
Frequently asked questions
Can the extension read my passwords or session cookies?
Page-reading filters exclude password fields and recognised credential patterns before results leave the page. Scripts also have filtering and approval controls. These measures cannot guarantee that every sensitive value is recognised; review the page and proposed action before sharing information.
Will it submit a form without asking?
Explicit submits, form-fill operations, clicks recognised as committing actions and scripts require approval. Review the preview and destination carefully; an ordinary interaction can also have effects determined by the website.
Does it work on every website?
Website design, permissions and security policies can limit reading or actions. Some sites block scripts; where possible, Metis can continue with supported reading and interaction tools.