grok-build ZDR

Appearance

grok-build ZDRYour agent. Your provider boundary.

Run the grok-build harness with explicit egress controls and provider configurations you can verify.

Get started
Provider support

ZDR-enhanced harness

Keep workspace tools and agent state local while allowing only the configured inference path to cross the boundary.

Multiple providers

Copy-ready recipes for OpenAI Responses, DeepSeek Chat Completions, and OpenCode Go endpoints.

Honest compatibility

Separate supported paths from provider-tested paths and planned Codex subscription authentication.

What this documentation covers ​

This site documents the ZDR-enhanced version of grok-build in this repository:

  • building and running the agent;
  • defining custom model providers in ~/.grok/config.toml;
  • selecting models from the CLI or TUI;
  • tightening the local data-egress boundary; and
  • testing OpenAI, DeepSeek, and OpenCode Go configurations without exposing keys.

Start with Getting started, then choose a provider from the support matrix.

Two different promises

The harness controls which application paths may send data. A provider's retention, training, and abuse-monitoring terms control what happens after an inference request reaches that provider. Confirm both before treating a deployment as end-to-end ZDR.

Documentation for the ZDR-enhanced grok-build harness.

Provider retention policies and model availability remain the provider's responsibility.