Coexistence with official grok
Run both CLIs on one machine without trampling each other.
Hyper is not affiliated with xAI. You can install it beside the official grok CLI. Binary and updater are isolated; runtime state is intentionally shared.
| Surface | Official grok | Hyper |
|---|---|---|
| Binary | grok | hyper |
| Managed install root | ~/.grok/bin | ~/.hyper/bin |
| Config / auth / sessions | ~/.grok | same ~/.grok |
| Leader IPC (sock / lock) | under ~/.grok | same namespace |
| Updater target | official install | only this repo’s Releases |
Implications
- Sessions, API keys, and OAuth scopes are shared — log in once if both CLIs can use that provider.
- Leader list/kill can see both products’ leaders. Prefer killing only leaders you started.
- hyper update and startup auto-update never overwrite ~/.grok/bin/grok.
- Re-running install.sh / install.ps1 is a supported recovery path for the Hyper binary.
Nothing in the official installer is rewritten by Hyper’s install script. Community builds opt into community-build branding and the isolated updater.