Ajutant for Chrome
Ajutant for Chrome puts your assistants in a side panel next to the page a person has open. They can use the page as context, and an assistant you allow can read, move between and act on pages for them. Anything that sends, posts or submits waits for the person to confirm.
Three people decide what happens, each at their own level:
- You (IT) turn it on and keep the list of sites it may never touch.
- The assistant’s author says which sites the assistant works on and what it may do there.
- The team’s admin approves that for their team, after looking at the author’s test runs.
The person in front of the page decides only about that page: whether the assistant may read it (they can switch reading off for a chat), and whether to let the assistant use a page outside its sites.
Turn it on
Section titled “Turn it on”Go to Admin → Governance → Browser extension and, under Availability, switch it to Enabled for the organisation. While it is off, nobody can sign in to the panel. Switching it off again stops every panel at once: signed-in panels lose access at their next request.
Sites it may never touch
Section titled “Sites it may never touch”Add hosts under Blocked sites, with a note on why if you like. A blocked host covers its
subdomains: blocking bank.example also blocks login.bank.example.
On a blocked site the panel says your organisation does not allow it, and nothing on it is read. No assistant can read, open or act on it, whatever its author or a team admin allowed, and a person cannot grant it either. Changes apply to the next step of a run already under way.
Browser pages (chrome://), files opened in the browser and incognito windows are always
refused.
Confidentiality and retention
Section titled “Confidentiality and retention”Confidentiality tags give a host a level, such as confidential for your HR system. A page
is used only when the team and assistant are cleared for its level, as with documents.
Page excerpts with audit records decides what is kept of the pages the assistant read or the text it sent:
- Keep a bounded excerpt: a short excerpt is kept with each step, for the period your retention policy sets for that level, then removed. The step itself stays.
- Metadata only: no page text is kept at all; the step records the address, a fingerprint and the size.
Page text the assistant needed during a run is removed from the conversation when the run ends.
Limits and approvals
Section titled “Limits and approvals”Steps per run and Minutes per run cap a run (40 steps and 10 minutes of active work by default). Time spent waiting for the person does not count.
Off-scope permission lasts sets how long a page or site a person allowed stays allowed, at most until they sign out of the panel.
Switch on An assistant’s page capabilities must be approved by someone other than its author to stop authors approving their own assistants for a team.
What it did
Section titled “What it did”Admin → Monitoring → Browser extension lists every run: who, which assistant, which team, where it started, how many steps, and how it ended. Open a run to see each step in order: what was read or done, on which page, why a step was refused, and, at each review, what was sent and which pages informed it. Viewing an excerpt is itself recorded.
Team admins see their own team’s runs on the team page, under Browser activity.
Model usage from the panel is part of your usage and cost reports, attributed to the team the conversation acts for. Filter cost reports by surface to see the browser extension on its own.