Diagnostics & support bundles

When something misbehaves, a diagnostics bundle gives whoever’s helping you the facts they need — versions, recent errors, configuration — without exposing anything you typed. Building and sharing one is always your choice.

Building a bundle

Settings → Diagnostics builds a bundle. It’s also available over the API at GET /api/v1/diagnostics and follows the shared diagnostics-bundle.v1 contract.

What’s inside

• Build identity — app build id, git SHA, and dependency/runtime-pack versions.
• Hardware — SoC and unified memory (the same as Settings → Hardware).
• Recent logs — at the log level you set, including recent errors.
• Effective configuration — your settings with secrets removed.
• Model/runtime state — which packs and capabilities are active.

What’s redacted

The bundle is built to be shareable. It strips:

• Prompts and chat content.
• Document and file contents, and file paths where they’d reveal sensitive structure.
• Secrets — Hugging Face tokens, access keys (these live in the Keychain and never enter a bundle or export).

Log levels

Raise the log level in Settings → Diagnostics before reproducing a hard-to-catch issue, then build the bundle so the extra detail is captured. Lower it again afterward — verbose logging is noise during normal use.

Sharing it

Attach the bundle in the community with a description of what you did and what happened. Because it carries versions and errors but not your content, you can share it without leaking prompts or files. The privacy guarantee is the same as everywhere else: nothing leaves your Mac unless you send it — see Network calls.

See also

• Troubleshooting — try these first.
• Community & support — filing a good report.
• Data & file locations — where logs live.