Diagnostic Packet

Vol. 01 · Local edition

Open packet format · No telemetry

A bug report they can replay.

Collect the versions, hashes, redacted logs, and reproduction steps maintainers actually need—then inspect every byte before it leaves your machine.

cargo install diagnostic-packet
Walk through a packet Read the source
  • Local only
  • Explicit consent
  • Single binary
An editorial arrangement of diagnostic papers with black privacy redactions and a closed archive envelope
Fig. 1 Scattered local evidence, assembled for review.

The missing context

“Which version? Which config? Can you send the log—without the token?”

Diagnostic Packet turns that follow-up loop into a manifest your project can version and every reporter can preview.

01 / Method

Four deliberate steps.
No background surprises.

  1. 01

    Preview

    Validate the manifest and print the exact collection plan. Nothing runs.

  2. 02

    Capture

    Run only allowlisted version checks you approve. Redact before writing.

  3. 03

    Inspect

    Review staged HTML, JSON, logs, sizes, and SHA-256 fingerprints.

  4. 04

    Export

    Seal the unchanged review directory into a portable, self-contained ZIP.

02 / Proof desk

See what gets collected.

This sample is fixed and stays in your browser. Use the arrow keys to move between stages.

diagnostic-packet.tomlLocal
format_version = 1
title = "Editor startup failure"

[[collectors]]
id = "node"
type = "tool-version"
command = ["node", "--version"]

[[collectors]]
id = "editor-log"
type = "log"
path = ".logs/editor.log"
Collection planNo data read

03 / Redaction desk

Private by construction.

token=████████████

Redact before disk

Tokens, emails, IP addresses, and home paths are replaced before evidence reaches the packet directory.

Hash, don’t copy

Configuration collectors fingerprint lockfiles and settings without copying their contents.

Consent is explicit

Preview runs nothing. Version commands use exact safe flags and still require approval during capture.

04 / The manifest

Version the questions you always ask.

A project-owned TOML file turns maintainer knowledge into a repeatable checklist. Collector types are closed and paths cannot escape the project root.

system
OS family and architecture
tool-version
Approved version commands only
config-hash
SHA-256 without file content
log
Bounded, redacted text copy
environment
Explicit safe variable names

Ready for the next incident

Send evidence.
Not guesswork.

cargo install diagnostic-packet

Free, open source, and local by default.