Where you can talk to it

There is one assistant with one memory of you. What changes between surfaces is where you are standing and what it can already see.

The full chat

Ask Metis, under the search field in the sidebar, opens the full chat. This is the richest surface: everything in the library, everything in your own data, attachments, the web, calculations, scheduling, and your whole conversation history.

Start here when the question is not about one particular thing you have open.

The chat beside a document

Open an Airworthiness Directive, a Safety Information Bulletin or a reportable occurrence, and the chat sits next to it, already having read what you are reading. No copying, no explaining which document you mean.

This is the same full chat — the same model modes, attachments, renaming, history, inline citations and automatic source-checking. Nothing is stripped down because you are inside a module. A card at the top of the thread names what is loaded, for example "AD 2026-0117 · Main document loaded".

Leave and come back later and your last conversation about that document resumes; or start a new one. Either way it appears in your Conversations history, badged with what it was about, and Open in full chat carries the same conversation over to the main chat page.

On a phone the page becomes a switcher — document or chat, one at a time — with an "Ask about this" button that jumps to the chat.

Where a document is an image-only scan, the text is extracted automatically the first time its chat is opened. If that is not possible, Metis is told plainly that the text could not be read, so it answers from the document's metadata rather than guessing at contents it cannot see.

"Ask in chat" from a record

Trackers, procedures, registers and form templates each have an action on their detail page that opens the full chat already scoped to that item.

What it receives automatically is a short summary — a tracker's identity, a procedure's title, version, lock status, step count and last run, a register's fields and item count, a template's fields and submission count. The actual rows, steps and values stay behind a lookup it calls when it needs them, so your whole register is not dumped into every reply.

Grounding is access-checked. If you do not have access to the item, nothing is grounded — the deep link is not a way around permissions.

Guided methods

Three places open the chat with a method already loaded, because the work has a defined shape worth following:

• Risk assessments — the chat sits beside the bow-tie editor and follows the risk-assessment method.
• Airworthiness Directives and Safety Information Bulletins — an AD is a mandatory determination and a SIB is advisory and operator-decided, so each gets its own method rather than one blurred into the other.
• Occurrence reporting reference — reportability and the reporting fields.

Everywhere else, the chat is simply the chat.

Your browser

The browser extension is the same assistant working inside a page you have open, in your own logged-in session — reading a page, filling a form, clicking. It is how Metis reaches the systems that are not Avioverse: your ERP, an authority portal, a supplier's site.

It will not submit, save or send without your explicit approval, and it cannot read your passwords or session cookies. It has its own page, because the detail matters: The browser extension.

Your phone

Pair Telegram from Settings → Integrations and you can reach the same assistant from your phone, including by voice note. Only paired accounts are served.

Telegram has the same capability as the full chat — the same tools, the same methods, the same memory. The differences are the medium: replies are more compact, and there are no in-app deep links.

What is not there

Metis does not send email. There is no outbound mail capability, on any surface.