-
Notifications
You must be signed in to change notification settings - Fork 0
Installation
-
Download the unpacked ZIP and
SHA256SUMS.txtfrom the matching GitHub Release. -
Verify SHA-256 in PowerShell:
Get-FileHash .\Project-Constellation-v0.14.0-unpacked.zip -Algorithm SHA256
-
Extract the ZIP to a permanent directory. Chrome expects that directory to remain available.
-
Open
chrome://extensions. -
Enable Developer mode and select Load unpacked.
-
Choose the extracted directory containing
manifest.json. -
Confirm the extension ID is
geljambmkfjkhodgkpjhnmfojkpcamig. -
Pin the extension, open Project Constellation, and visit Accounts & Connections.
Do not load the source repository root; load build/unpacked during development or the extracted release directory for normal use.
The stable manifest key and storage schema preserve the extension identity and local browser data. Extract v0.14.0 to a new permanent folder, open the existing extension’s details in chrome://extensions, and reload it from the new unpacked folder. Do not remove the old extension first unless you already exported or remotely verified the local brain; removing an extension can delete its browser storage.
After reload:
- Open Home and check the status bar/catalog counts.
- Open Accounts & Connections and verify provider sessions.
- Reconnect Google/GitHub only if verification reports authorization missing/expired.
- Run Round-trip verify for Drive.
- Open an existing ChatGPT chat and confirm Execution Pulse plus its permanent ⇄ Output Vault control appear.
Run npm run build:dev, then load build/unpacked. Development builds are clearly labeled and deliberately contain no OAuth configuration unless valid client IDs were provided. Use them for local UI/capture testing, not production OAuth acceptance.
Before removing the extension, export the local brain and/or complete a verified Drive sync. Verify the resulting receipt and remote snapshot. Then remove the extension from chrome://extensions.