Portable setup manager for the current xAI Grok Build terminal agent.

This module manages an explicit, absolute Grok Build home. It never defaults to live ~/.grok, never invokes live Grok Build during setup/profile switching, and preserves unmanaged state in the target.

Use cli-tools/nddev_grok_build.py --help for the current command surface. Commands that mutate or inspect managed state require an explicit absolute target. update refreshes the currently installed setup/profile identity from the module sources; update-cli refreshes target-owned Grok Build software.

install-cli, update-cli, and remove-cli manage target-owned Grok Build without touching setup, auth, or unrelated target state. Install and update use verified official npm tarballs for the umbrella package and selected native package. Package scripts are not run; the official installer is retained only as source metadata. The current version, package integrity, installer observation, and materialization bounds are code-owned in build/version.json, references/grok-build-baseline.json, and cli-tools/nddev_grok_build.py. All target-bound setup, software, status, plan, restore, remove, and launch commands reject unsupported hosts before target resolution or runtime side effects. Product runtime management is scoped to macOS and Ubuntu hosts.

The content setup is nddev-builder. It enables maximum documented builder capabilities inside the isolated managed GROK_HOME: memory, subagents, web fetch, LSP tools, file writes, tool search, native skills, native plugins, and a target-local Grok marketplace. It also disables Grok config auto-update and envrc loading for the pinned runtime.

Permission profiles are orthogonal:

• full-auto: native always-approve, sandbox off, no managed permission deny rules.
• safe: native ask, sandbox strict.

Legacy schema-1 setup ids safe, balanced, and full-auto are readable for status, migration, restore, and removal only. Legacy state is never launchable.

The public NDDev Builder toolkit lives under builder/nddev-builder/plugins/nddev-builder. The manager projects the full regular-file toolkit into:

• $GROK_HOME/skills/
• $GROK_HOME/agents/
• $GROK_HOME/plugins/nddev-builder/
• $GROK_HOME/plugins/marketplaces/nddev-builder/

The local marketplace manifest is builder/nddev-builder/.grok-plugin/marketplace.json; its plugin source is a relative path to the sibling plugin tree. Plugins and marketplaces deliver Grok content files only, not native binaries or external runtimes.

launch executes only the target-owned <target>/bin/grok with GROK_HOME=<target>, target-local child HOME and TMPDIR, auto-updates disabled, and provider credentials stripped from the inherited environment. It rejects Grok Build flags that override managed target, session, model, permission, sandbox, tool, plugin, cwd, or system-prompt scope and never falls back to PATH.