mycliq.Back to the main site

Beta tester download

Development candidate—not Store-approved; some workflows are still being tested. This is a manual tester installation, not an automatic Chrome Web Store update.

Download this exact candidate, check its checksum, then follow the instructions below. A checksum confirms matching bytes; it does not prove that every workflow has passed testing.

Download beta ZIP · 0.1.16

mycliq-beta-0.1.16-703c6e0f3c04.zip · 7,219,818 bytes

Which build is this?

Version
0.1.16
Installed name
CLIQ v5 (dev)
Source
703c6e0f3c04a5e6017578b470729c55e2be15b2
API
https://cliq-xi.vercel.app
Extension ID
dcefdhddnglckbjjbdjfiijfcfgkekjo

Check your download

Compare the downloaded ZIP before extracting it. If either checksum differs, do not install that file; download it again.

MD5 parity
919004ebe2dce736527c20284262e985
SHA-256
8fd425f27f534a5588a7e19c62d347379a46b6973e520fd1b9501b7be7791295
Download MD5 fileDownload SHA-256 fileCandidate details (JSON)

MD5 is provided for download parity, not security or publisher authentication. SHA-256 is also provided for stronger integrity checking.

Windows PowerShell

Get-FileHash -Algorithm MD5 ".\mycliq-beta-0.1.16-703c6e0f3c04.zip"
Get-FileHash -Algorithm SHA256 ".\mycliq-beta-0.1.16-703c6e0f3c04.zip"

macOS / Linux

On macOS, use md5 and shasum -a 256 with the ZIP filename. On Linux, use md5sum and sha256sum.

Install in Chrome or Edge

  1. Download and verify the ZIP above. Extract it once into a permanent folder. The folder you select must contain manifest.json.
  2. In Chrome, enter chrome://extensions in the address bar. In Edge, enter edge://extensions.
  3. Turn on Developer mode, choose Load unpacked, and select the extracted folder—not the ZIP.
  4. Check that the extension ID matches dcefdhddnglckbjjbdjfiijfcfgkekjo. If it does not match an existing installation, ask in your beta thread rather than installing competing copies.
  5. Open the add-on and sign in using the access provided by the team. Missing access is a setup issue to report, not a reason to create test accounts or send test invitations in production without approval.

Managed browsers may not allow Developer mode. Ask your administrator rather than changing browser security policies.

Official Chrome instructionsOfficial Edge instructions

Update an existing tester installation

  1. Back up the current extracted folder. Download the new candidate and compare its checksums.
  2. Replace the extension files in the same folder, then select Reload on the extension card. Refresh any test tabs.
  3. Do not uninstall the add-on, clear its storage or reset your browser profile just to update it. Tester updates are manual; check the version and source above after each release.

Go back to your previous tester build

Restore your backed-up files into that same folder and reload the extension. Keep the browser profile and stored data. If you did not save a backup, ask the team for the previous qualified tester package.

Client rollback is separate from server rollback. It does not undo server-side records or establish compatibility with an older API.