Internal distribution

Put the assistant on any government web page.

A browser extension for Chrome and Edge that draws the AI assistant onto the page in front of you. Nothing changes on the ministry's website, and it appears only on the sites you switch on, one at a time.

For services with no application programming interface to file against, it can also complete the ministry's own web form from a conversation a citizen already had — in a member of staff's signed-in session, stopping before Submit so that the last act on a government form is a person's.

Download

Unzip into a folder you will keep. The browser loads the extension from that folder every time it starts.

Google Chrome

Chrome 116 or later. Load unpacked from chrome://extensions.

Download for Chrome · 23 kB

SHA-256 0a6f7c6f0f7e35d2c6b2f868c882713b99b0bc66cc82ebcf01fea84a7d779f9f

Microsoft Edge

Edge 116 or later. Load unpacked from edge://extensions.

Download for Edge · 23 kB

SHA-256 7339dbf3ffe44f9edfad39b82de114d29f2fc68652d5cc59eea308093674f8c3

The guide

Installation, configuration, filling a form, and what a new ministry supplies. Ministry-agnostic throughout.

Installation Guide

English · 15 pages

Download PDF · 2.4 MB

دليل التثبيت

العربية · 14 صفحة

تنزيل الملف · 2.4 MB

Install in four steps

Unzip the package into a permanent folder, for example C:\Assistant\chrome.
Open chrome://extensions or edge://extensions and turn on Developer mode.
Press Load unpacked and choose the folder that contains manifest.json.
Open the extension from the toolbar, enter the platform origin and widget key your platform team gave you, then press Switch on for this site on the portal you want it on.

It holds no access to any website until you grant one. Access is requested per site, by name, at the moment you switch that site on — not once at install time over everything you will ever open. Switching a site off revokes it.

Verify what you downloaded

Compare against the checksum printed on the card above.

# macOS, Linux
shasum -a 256 assistant-extension-chrome.zip

# Windows PowerShell
Get-FileHash assistant-extension-chrome.zip -Algorithm SHA256

Deploying to an estate

Loading unpacked is right for a pilot and wrong for forty machines.

Route	When
By hand	A handful of people who can be told when there is a new version.
Browser policy	A ministry's estate. `ExtensionInstallForcelist` on both browsers, served as a signed `.crx` from a URL the organisation controls. The pinned identity in each build is what makes this work — the extension id is the same on every machine. Ask the platform team for the package and the update URL.
Public store	Not used and not planned. A public listing invites the public to install an internal tool.

Adding another ministry

Nothing here is specific to one ministry, and the extension is not forked to add one.

The ministry supplies	The platform team does
The portal's origin, exactly as served	Issues a widget key for it and adds it to the embed allowlist
A test account that can open the forms and file nothing	Captures each form into a site pack — one pack per portal, not per service
The services wanted, by the names the portal uses	Binds every field to a question the assistant already asks
Who will hold a staff token, if forms are to be filled	Sets the submit policy per service — the default stops before Submit

The portal it works on, the services it knows, the field names and the order of the steps are all data the extension fetches at run time. A new ministry is a new pack, not a new extension. Chapter 6 of the guide has the full sequence.