Gork Build (gork)

Gork Build: the VSCodium-style community build of Grok Build — research / product analytics hard-off

An independent, community-maintained distribution of SpaceXAI Grok Build with vendor telemetry hard-off and a community rebrand (compatibility identifiers such as ~/.grok, GROK_*, and API hosts are retained).

Privacy note: agent-selected model context (prompts, tool results, file contents the agent reads) still goes to the model API — that is how cloud coding works. Research uploads and product analytics are hard-off separately; they are not the same channel.

Install · Build from source · Privacy · Documentation · Contributing · License

Gork Build is to Grok Build what VSCodium is to VS Code, and what ungoogled-chromium is to Chromium.

This GitHub repository is not a full Rust checkout. Like VSCodium and ungoogled-chromium, it holds a patch queue, overlays, and CI that fetch a pinned xai-org/grok-build revision and apply privacy hard-offs. Compatibility identifiers (~/.grok, GROK_*, API hosts) are kept.

---

Comparison at a glance:

	Grok Build (upstream)	Gork Build (this fork)
License	Apache-2.0	Apache-2.0 (same code)
Agent / tools / TUI	Full	Full
Model inference	Yes (Grok API)	Yes (your credentials)
Mixpanel / product events	On by default in releases	Hard-off
GCS research / session traces	Upload pipeline present	Hard-off
Whole-repo research packaging	Present upstream	Disabled
Vendor auto-update	Yes (x.ai/cli)	Hard-disabled (rebuild / community releases)
Coding-data retention	Opt-in available	Opt-out only (locked)

---

Why this exists

Independent wire analysis of Grok Build 0.2.93 showed that research upload paths (session traces, and historically whole-repo snapshots) could leave the machine even when “Improve the model” was off — including secrets in files the agent read. Upstream open-sourced the harness; Gork Build re-ships that code with privacy by construction:

• No product analytics (Mixpanel / events telemetry)
• No client-side research / trace / session-state uploads to GCS
• Remote feature flags cannot re-enable those paths
• Coding-data retention is opt-out only (no opt-in path)
• Vendor auto-update is hard-disabled: Gork Build never installs from x.ai update channels (x.ai/cli/install.*); that path would replace this fork with official Grok Build. Update by rebuilding from source or installing community releases from this project.

What still leaves the machine: whatever the agent must send to the Grok model API to work (prompts + tool results for files it actually reads). That is required for a cloud coding agent and is separate from the research / product-analytics hard-offs. Gork Build does not add extra research packaging on top.

Install

Prefer a GitHub Release binary (gork-<tag>-<platform>.tar.gz / .zip). Those are the patched product builds. CI extracts every shipped archive and runs the binary (--version, --help, and update must refuse vendor installers) before the release is published, then re-downloads the published assets and smokes them again. Vendor x.ai/cli installers are hard-disabled — they would overwrite this fork with official Grok Build.

macOS binaries are unsigned:

xattr -d com.apple.quarantine gork

Put gork on your PATH. An optional grok alias is fine if you want the upstream command name.

Build from source

This repo is a recipe (patches + scripts), like VSCodium or ungoogled-chromium. Clone it, materialize upstream + patches, then compile:

git clone https://github.com/thedavidweng/gork-build.git
cd gork-build
python3 maint/scripts/patchctl.py checkout   # or ./scripts/dev.sh
# → .work/src  (gitignored product tree)

cd .work/src
# Rust toolchain: rust-toolchain.toml in this tree
# protoc: bin/protoc, a system protoc, or $PROTOC
cargo run -p xai-grok-pager-bin              # TUI binary: gork
cargo build -p xai-grok-pager-bin --release  # target/release/gork

On first launch, authenticate with your Grok / xAI account the same way upstream does — model access still goes through the Grok API.

What's in this repository

Path	Role
maint/patches/	Privacy / identity patch series (the delta vs upstream)
maint/overlays/	Community README, PRIVACY, assets applied on checkout
maint/upstream.lock.toml	Pinned xai-org/grok-build SHA + version
maint/scripts/patchctl.py	checkout, apply, export, lint, sync
.github/workflows/	Privacy contracts, replay, community releases
.work/src/	Not committed. Created by checkout.

Edit behavior in .work/src, then from the repo root:

python3 maint/scripts/patchctl.py export --tip HEAD

That rewrites maint/patches/. Do not expect a crates/ tree on main.

Privacy guarantees (client)

Channel	Gork Build behavior
POST …/v1/responses (model)	Used for inference only
POST …/v1/storage research traces	Never enabled (resolve_trace_upload → false)
Mixpanel / product events	No-op / never constructed
Sentry	Only if you set SENTRY_DSN yourself
Vendor auto-update (x.ai/cli/install.*)	Hard-disabled — rebuild from source / community releases
is_data_collection_disabled	Always true in this build

See PRIVACY.md for details and residual risks.

Configuration tips

# ~/.grok/config.toml — all of these are already the Gork Build defaults
[features]
telemetry = false

[telemetry]
trace_upload = false
mixpanel_enabled = false

[cli] auto_update cannot re-enable vendor channels: this build never installs from x.ai (enforced at the install chokepoint). Rebuild from source or use community releases.

Documentation

Feature docs ship with upstream and appear after checkout:

.work/src/crates/codegen/xai-grok-pager/docs/user-guide/

Or read the same tree on xai-org/grok-build.

Contributing

External contributions are welcome. See CONTRIBUTING.md for setup, commit style, and PR expectations. Security reports: SECURITY.md.

Made with Grok 4.5

Relationship to upstream

Gork Build tracks xai-org/grok-build. CI fetches a locked upstream SHA, applies maint/patches/, and publishes community binaries. When the series applies cleanly, a draft PR updates only the lock and patches — not a wholesale copy of the upstream tree.

Credit: original Grok Build is developed and published by SpaceXAI under Apache-2.0. Gork Build is an independent community distribution and is not affiliated with, endorsed by, or sponsored by SpaceXAI or xAI. Grok, Grok Build, xAI, and SpaceXAI are trademarks of their respective owners.

License

Apache License 2.0 — see LICENSE and attribution in NOTICE.

Upstream copyright (SpaceXAI) is retained as required by Apache-2.0. Community modifications are copyright the Gork Build contributors.

Security

Please do not open public issues for security reports that include secrets. See SECURITY.md.