Report what happened.

Local diagnostics

Collect a support bundle.

In the backend checkout, run:

make support-bundle

The command prints the path to a private support-bundle.tar.gz in a new temporary directory. It collects bounded diagnostics locally. It does not upload anything, start or restart services, initialize configuration, or inspect your browser or editor profile.

Python and Make are the collector's prerequisites. On Windows, run it in the same WSL distribution and backend checkout used to start CodeSecurity. It does not collect Windows editor logs automatically.

Review the extracted files before sharing. A support bundle is diagnostic material, not proof that its contents are safe to publish. Keep the default summary-only bundle when further review is impractical.

If your installation uses a custom state directory, follow the full bundle instructions so the collector observes that same installation.

Describe what happened.

1. Give the platform, source revision and extension version. Distinguish native Windows VS Code from Remote WSL.
2. Describe the action and time, expected result and actual status. Include the exact error after checking it for private information.
3. Say whether the issue persists after the documented recovery step. Do not bypass source, credential or completeness checks.
4. Attach only reviewed diagnostics. For extension-only issues, share the relevant bounded CodeSecurity Output entries, not the entire VS Code user-data directory.