Core concepts
Understand what is captured, what is shared, and what a replay can establish.
Reproduction
A reproduction is a captured application failure with its source files, runtime profile, and recorded evidence. It belongs to an organization and opens in a triage workspace.
Reproduction bundle
The bundle contains the selected source files. Command capture preserves the source from before execution. For a monorepo, selection includes the app, its declared internal dependencies, and workspace configuration. This follows declared dependencies, not a trace of which files executed.
Capture signature
The capture signature records the observed failure, including output, stack frames, timing, and browser diagnostics when available. It supplies evidence for investigation and, when complete and supported, a baseline for clean replay.
Triage workspace
The triage workspace is where engineers inspect source, captured evidence, and live sandbox behavior. Captured logs describe the original observation. A live terminal acts on the sandbox now.
A terminal session has one active driver who can send shell input. Other connected participants are read only viewers.
Sandbox
A sandbox is an isolated environment for investigating a reproduction. Its dependencies, environment values, services, and network access can differ from your machine. Starting a sandbox is not proof that the original bug reproduced.
A child reproduction is created from a snapshot of a reproduction's live sandbox and retains a relationship to its parent.
Clean verification
Verification prepares captured source in a fresh environment and attempts to replay the selected failure. Static readiness checks identify known missing inputs. They do not execute the application or establish reproducibility.
A replay may match, drift, fail during setup, or be unavailable. Read the verification report and its evidence rather than treating a score as a guarantee.