Scoop bucket for Companion Intelligence desktop apps.
Get started · Systems map · Documentation
| Feature | What it provides |
|---|---|
| Windows install manifest | Download the Hub installer and run the silent setup. |
| Release tracking | Follow GitHub Hub releases rather than building the app here. |
| User data | Preserve user data during Scoop upgrades and uninstall hooks. |
The bucket tracks the Companion Hub installer release and delegates installation to the Windows setup program; the bucket preserves user data during upgrades.
flowchart LR
HubRelease[Companion Hub release] --> Manifest[Scoop manifest]
Manifest --> Installer[Silent Windows installer]
Installer --> App[Companion Hub on Windows]
scoop bucket add companionintelligence https://github.com/companionintelligence/scoop-bucket
scoop install companion-hubscoop update companion-hubcompanion-hub.json is generated from Companion-Hub distribution/ on each Hub desktop release. The other manifests in this bucket (companion-memory, companion-capture) are maintained by hand.
Companion Memory runs its server in Docker: install and start Docker Desktop (or another Docker engine with Compose 2.24.4 or newer) first. The first launch pulls about 3 GB of container images.
scoop bucket add companionintelligence https://github.com/companionintelligence/scoop-bucket
scoop install companion-memoryUpdate with scoop update companion-memory. The manifest is bumped by hand for each desktop-v* release. Companion Memory is installed by its own setup program, so Scoop cannot remove it: uninstall it from Windows Settings > Apps. Uninstalling does not stop its containers or delete the Docker volumes that hold your memory.
| Item | Behavior |
|---|---|
| Platform | Windows x64 installer |
| Install | Scoop runs the Hub installer silently |
| Version source | Manifest checks Companion Hub GitHub releases |
| Upgrade and uninstall | User data is preserved; the uninstall hook removes only managed Docker containers and networks |
Scoop may run uninstall hooks during upgrades, so the manifest intentionally avoids deleting persistent application data. Back up Hub data using the Hub's own backup workflow before manually removing it.