Skip to main content
MV2 is a legacy build for Chromium forks with version below 88 (e.g. older Cent Browser). If your workstations run Google Chrome, Microsoft Edge, or any browser with Chromium >= 88, use the Manifest V3 installation instead.
Audience: Hospital IT and Information Security teams. This guide covers the Manifest V2 build — only for Chromium forks with version < 88.

​
Extension ID

This is the 32-character identifier derived from the MV2 build’s public signing key. Different from MV3 because each build is signed with its own key.

​
Prerequisites

  • Workstations run a Chromium fork with version < 88 (e.g. Cent Browser on older Chromium)
  • HTTPS outbound connectivity to cdn.telepatia.ai is allowed (port 443)
  • A policy management platform is available (ManageEngine, Intune, GPO, or equivalent)
To confirm the Chromium version: open cent://version (or equivalent). The Chromium version (not the product version) determines the MV2/MV3 decision.

​
Policy Snippet

​
Fields

​
Blocking other extensions (optional)

​
Obtaining the CRX

1

Check the manifest

Open https://cdn.telepatia.ai/scribe-extension/update-manifest.json.
2

Download the MV2 CRX

Use the URL from the v2.crx.downloadUrl field.
3

Verify integrity

Compare with v2.crx.sha256.

​
Deployment via ManageEngine Endpoint Central

1

Navigate to Browsers → Manage → Extension Repository

2

Add Extensions → Add Extensions for Google Chrome → Upload Directly

3

Upload the MV2 CRX file

Confirm the Plugin Identifier matches blohhkgibpajgnknfeokemldajkpnfjg.
4

Apply policy to target hosts/groups

5

Wait for propagation

6

Validate (see below)

​
Deployment via GPO

1

Open Group Policy Management Console

Edit the GPO targeting the clinical workstations OU.
2

Navigate to Computer Configuration → Administrative Templates → Google Chrome → Extensions → ExtensionSettings

3

Enable and paste the MV2 JSON snippet

4

Link the GPO to the target OU

5

Wait for GPO refresh (~90 min) or gpupdate /force

6

Validate (see below)

The ExtensionSettings policy is respected by most Chromium forks that honor Chrome policy keys, including Cent Browser. For forks with custom policy parsing, validate in pilot first.

​
Network Requirements

Same requirements as MV3. See the MV3 guide for SSL inspection details.

​
Auto-Update

Same mechanism as MV3 — the browser checks for updates every ~5 hours. The update_url is the same endpoint; the manifest serves both MV2 and MV3 builds.

​
Post-Installation Validation

  • Open chrome://extensions (or fork equivalent)
  • Confirm Telepatia Scribe Companion appears
  • Confirm it says Installed by your administrator

​
Ongoing Operations

Same responsibility model as MV3. See the MV3 guide.

​
Support

Same channels as MV3. Report unexpected behavior during installation through the agreed Telepatia channels.