Install the Grok CLI

Olivares AI installs the official Grok Build CLI. It does not vendor a copy of Grok and it does not replace grok.

1. Install or verify

olivares agent tool detect --driver grok --probe
olivares agent tool plan --driver grok --version stable
olivares agent tool install --driver grok --version stable --yes
olivares agent tool list -o json

Ask for the channel the origin publishes. The Grok origin publishes stable. It answers HTTP 404 for latest, and Olivares then refuses with version_unknown and prints the URL and the status. Channel names belong to the vendor.

The receipt records the version, the measured digest, the --version probe, and the verification class. Probe is not authentication. Presence of ~/.grok/config.toml is reported as file presence only.

Verification class (honest): Grok origin-install is none-origin-only. Olivares fetches from the official HTTPS origin, places bin/grok, and probes --version. That is not a publisher signature. The receipt says so.

macOS and Windows are not offered in this increment.

2. Managed configuration

olivares grok managed-config --policy policy.json \
  --requirements-out /etc/grok/requirements.toml

Grok clamps /etc/grok/requirements.toml as the highest layer (sandbox profile and MCP allowlist). A user can still disable a hook by writing its name in ~/.grok/disabled-hooks; that file is observe-only.

See Integrate Grok Build for the can-enforce versus can-only-observe table.

3. Launch and stop

Pin the official binary, or use a managed install receipt:

export OLIVARES_SESSION_RUNTIME_GROK_BIN=/var/lib/olivares/tools/grok/<version>-<platform>/bin/grok

If that variable is unset, the session runtime uses the newest verified managed install, then grok on the engine’s PATH. It resolves the program at launch.

olivares agent session create --name "grok-work" --workspace ws-123 --provider-profile prof-123
olivares agent session stop run-123

Create and stop go through the sessions API and leave a managed run record. Compatibility with an authenticated official Grok account is not claimed here.

4. Requirements and limits

Each step of a Grok Build session, measured on the engine with the official CLI (the container image contents are read from its Dockerfile):

Step	What to know
Install	olivares tool install grok takes the stable channel from the official origin. The check is origin-only, as above.
Bind	Grok Build runs only on an xAI key. Leave the endpoint empty for https://api.x.ai/v1. A custom base_url is used as given, so it ends in /v1. Plain HTTP is accepted only at a loopback or private-network address, for a local xAI-compatible server.
Start	On Linux, the ask, read-only, edits-only and edits-and-commands presets run Grok’s own sandbox, which needs bubblewrap (bwrap). Without it the start is refused before anything runs, and the message names the package. The official container image does not ship bubblewrap, so install bubblewrap on the engine’s host to start Grok Build sessions.
Answer, stop, resume	A resumed session continues the same conversation.

Further operate rules: Operate a provider session.