Glob for the command line

Install with the one-line installer. It detects your architecture (Apple silicon or Intel), downloads the matching build, verifies its checksum, and installs to ~/.local/bin/glob:

curl -fsSL https://install.colli.dev | sh

The macOS build is a universal binary, published under both architecture names so the installer always finds a match. Prefer a direct download? Pick your version from the releases index — archives are named glob-v<VERSION>-<os>-<arch>.tar.gz:

• glob-v<VERSION>-darwin-arm64.tar.gz
• glob-v<VERSION>-darwin-x86_64.tar.gz

Same one-line installer for x86_64 and arm64 — it installs to ~/.local/bin/glob and verifies the checksum before running anything:

curl -fsSL https://install.colli.dev | sh

On Linux x86_64 the installer defaults to a fully-static (musl) build. That build cannot use the system certificate store, so glob login, glob ask, and glob sync fail over HTTPS. For those commands, install the dynamic build with GLOB_INSTALL_DYNAMIC=1 (needs the Swift runtime). Linux arm64 ships only the static build. Static archives are named glob-v<VERSION>-linux-x86_64-static.tar.gz and glob-v<VERSION>-linux-arm64-static.tar.gz.

Not available yet — the CLI currently targets macOS and Linux.

Every release folder at install.colli.dev/releases ships a SHA256SUMS manifest alongside the archives. To check an archive you downloaded by hand, fetch the manifest for its version and run:

cd ~/Downloads
curl -fsSL -O https://install.colli.dev/releases/<VERSION>/SHA256SUMS
shasum -a 256 -c SHA256SUMS

The one-line installer does this check for you — it refuses to install on a checksum mismatch.

Point Glob at your server, sign in, and confirm:

glob server set https://<your-server>   # or export GLOB_SERVER_URL
glob login --stdin                    # session token on stdin; or --email, or --web
glob status

glob login accepts a session token (--stdin), an email and password (--email --password-stdin), or a browser portal (--web). glob keys create issues an API key for agents; it is not a login session.

One passphrase per account, entered on each device. Set GLOB_SYNC_PASSPHRASE, or pass --passphrase-stdin. The passphrase never goes to the server; it unlocks the keys that seal uploads. Records in ~/.glob/store/knowledge.sqlite are stored in the clear:

export GLOB_SYNC_PASSPHRASE="pick-a-strong-secret"   # same on every device
# alternative: glob sync now --passphrase-stdin
glob sync now       # push and pull sealed document packages
glob sync status    # cursor, pending outbox, quarantined records, push failures

Re-run the installer — it replaces the existing binary with the latest version in place:

curl -fsSL https://install.colli.dev | sh

The CLI installs to your home directory — no root needed — so removing it is a few commands:

rm ~/.local/bin/glob ~/.local/bin/glob-tui
rm -r ~/.local/share/glob-tui
rm -r ~/.glob          # local store (plain records in store/knowledge.sqlite); Linux also credentials
rm -r ~/.config/glob   # Linux server config; macOS: ~/Library/Application Support/Glob

On macOS the session token is in the Keychain (service com.Glob.CLI, account glob_api_session_token), not in ~/.glob. Removing the directory does not delete that token.