Contact — SynapTrace

Something crashed, a view is empty, capture stopped, or an upgrade lost state.

Trajectory grouped the wrong work, a Gap Map entry felt off, Teaching missed the point — say so.

Questions about the license terms, internal organizational use, or what leaves your machine.

WHAT TO INCLUDE

A good bug report

SynapTrace version — 0.3.0 is current; VS Code shows the installed version on the extension page.
Your OS and VS Code version. The preview targets Windows x64.
Which view the problem is in: Trajectory, Changes, Gap Map, Teaching, or Settings.
What you expected to see, and what you saw instead.
Whether AI-assisted CLI analysis was enabled, and which provider and model were configured.
Sanitized diagnostics from Settings → Diagnostics, if the problem is reproducible.

BEFORE YOU SEND

API keys or provider credentials. They are never needed to diagnose a problem. SynapTrace keeps them in VS Code SecretStorage and they are excluded from diagnostics output.
Proprietary source files. Diagnostics are sanitized precisely so you don't have to send code.

Answers usually take a few days. There is no support SLA on a free preview, and it would be dishonest to imply one.