Run grok setup for managed configuration

grok setup fetches and installs managed configuration for the CLI. Official: CLI Reference. Use it when your org ships managed defaults; pair it with the enterprise layer map when you are rolling Build out on managed machines.

Run setup

grok setup

The subcommand installs managed configuration onto the machine. After it finishes, verify discovery:

grok inspect

Where managed config lives

Grok merges five layers (low → high priority). Official: Enterprise Deployments.

Priority	Path	Role
1	/etc/grok/managed_config.toml	System-wide managed defaults
2	~/.grok/managed_config.toml	Per-user managed defaults
3	~/.grok/config.toml	User preferences
4	~/.grok/requirements.toml	User-level pins
5	/etc/grok/requirements.toml	System-level pins (MDM / golden images)

requirements.toml pins cannot be overridden by user config, env vars, or remote settings. Many fleets push /etc/grok/requirements.toml with MDM or bake it into golden images instead of (or in addition to) running setup on each laptop.

Related paths

• Day-to-day personal defaults: Edit user config.toml in Grok Build
• Full enterprise rollouts (network, auth, ZDR): Deploy Grok Build for enterprise
• What this directory loaded: Inspect what Grok Build loads

Pitfalls

• Use grok login for auth and grok update for CLI versions; keep grok setup for managed configuration only.
• Do not invent remote URLs or flags beyond grok setup / grok setup --help on your installed CLI; pin versions with grok update when you need a specific build.