embabel bugreport [directory]

One folder to attach to an issue, instead of six rounds of “and can you also send…”. It holds doctor, status and version exactly as they printed, versions.json, the container list, what Docker says about itself and its disk, and per-container logs.

What is deliberately not in it. This appliance holds someone’s email, contacts and documents, so a diagnostic bundle is an exfiltration shape if it is careless. Two rules, both enforced in code rather than left to a warning:

• .env values are never copied. env-keys.txt lists the keys and whether each holds anything — “is OPENAI_API_KEY set” is a real diagnostic question; “what is it” never is. A key that is empty and a key that is absent are different bugs, so both are reported.
• Logs are filtered to warnings, errors and stack traces. An INFO line from this server can carry a document title, a contact’s name, or the text of a query somebody typed.

The bundle is left unpacked beside its .zip so it can be read before it is sent. A bundle you cannot inspect is one people send blind, or not at all.

Flag
--all-logs	full logs, not just warnings and errors — the bundle’s README.txt then says so in the first paragraph