# Support

## Before you write

1. Run `npx starwisp doctor`. It re-checks everything the installer needs and prints a fix for each failure.
2. Search [troubleshooting](troubleshooting.md) and [install](install.md) for the exact message you see.
3. Check [faq](faq.md).

## How to reach us

Email and the support form are on <https://getstarwisp.com/support>. Expect a reply within 2 business days (a target, not a guarantee). A known-issues list on the same page covers problems we already know about.

**Never send a key, token, password, `.p8`, `.pem` or service-account file, to us or anyone.** If you pasted one by mistake, revoke it at the vendor and make a new one. See each page under `vendors/`.

Include:

- what you were doing, and the exact message;
- the output of `npx starwisp doctor`, and of the failing command with `--debug` added (the installer never prints your keys);
- your Starwisp version (`npx starwisp --version`);
- the diagnostics file below.

## The diagnostics download

**Settings → Support → Download diagnostics** in the console builds one JSON file for you to read and attach. It is built from an allow-list, so it contains only:

- the product version and the version of each settings file;
- your presets;
- the **names** of your secrets and when each was last updated, never their values;
- the names of your repository variables;
- the Vault check results (the plain-language sentences);
- links to the last few failed runs and the names of the jobs that failed;
- the GitHub App's permission list (when GitHub lets the console read it);
- whether each console setting is present (yes or no).

It does **not** contain: any secret value, Actions logs, run titles (they hold your idea text), console Worker secrets, sign-in tokens, or raw vendor responses. The file also passes a filter that removes anything that looks like a key (for example `sk-ant-`, `cfut_`, `ghp_`, `github_pat_` or `-----BEGIN`); if anything still slips through, no file is produced. Open it and read it before you send it. It is yours to review.

Also send the `doctor` output and the failing step's message.