Install DRC

Install an application SDK through npm, or install the CLI through npm. macOS and Linux users can initialize a local workspace; the experimental Windows x64 CLI creates its local evidence directory when capture starts.

Prerequisites

• macOS or Linux
• Windows x64: experimental native CLI. Only drc run (explicitly routed HTTP to one local application port) and drc diagnose are available; HTTPS interception, passive process capture, and the other Unix CLI commands are not supported.
• An application with a development port you can proxy

For hosted use, also prepare an API URL and an authentication token. Do not put tokens in shell history, source files, issue descriptions, or support bundles.

Install an application SDK

Install only the package your application needs:

npm install @hypercubs/drc-sdk
npm install @hypercubs/drc-express     # Express middleware, when applicable
npm install @hypercubs/drc-browser     # browser capture, when applicable

Install the CLI

The CLI is published to the public npm registry:

npm install -g @hypercubs/drc

npm places the drc binary on your PATH. Verify the install with drc --version. The npm package is the only supported installation source; do not build the CLI from a source repository.

Initialize local storage (macOS and Linux)

drc init

Initialization creates the local workspace and reports the selected storage path. Local capture requires a managed signing key; do not use an ephemeral key for a durable workspace.

Capture HTTP on Windows x64

The experimental Windows build supports only drc run and drc diagnose. It records partial evidence for HTTP requests explicitly routed to its loopback proxy; it does not intercept HTTPS or capture application traffic automatically. Start the proxy with the application port as the target:

drc run --host 127.0.0.1 --port 8080 --target-host 127.0.0.1 --target-port 3000

Route the application's HTTP client to http://127.0.0.1:8080, replacing 3000 with the application's actual port. Press Ctrl+C to stop capture cleanly. Evidence is stored under .drc/storage by default.

Request and response bodies are omitted unless you explicitly pass --capture-bodies. That option captures only JSON objects or arrays with a JSON content type and masks fields whose names match a heuristic; it does not inspect arbitrary values for secrets and cannot guarantee redaction. Treat captured bodies as sensitive data and use the option only with approved, non-sensitive development traffic.

Verify the installation

drc diagnose

On Windows x64, drc diagnose reports the local CLI capabilities without claiming that a hosted control plane is healthy. On macOS and Linux, run drc doctor and drc search --format table. A command that cannot complete returns a non-zero exit status.

Connect a hosted workspace (macOS and Linux)

drc login --api-url https://api.drc.sh --email [email protected]
drc whoami

Use the hosted API URL supplied by your organization for private or self-managed deployments. Hosted requests require a tenant-scoped token. Hosted login commands are not available in the experimental Windows CLI. There is no drc config get command; see Configuration reference for environment settings and inspect .drc/drc.toml for local capture configuration.

Troubleshoot

• Command not found: ensure the installation directory is on PATH.
• Signing-key error: configure the managed local signing-key path and make the file readable only by the DRC process.
• API authentication error: verify the API URL, token expiry, tenant membership, and local clock.
• No executions: capture traffic through the DRC proxy before searching.

Next, follow Capture and replay an execution.