Get help with SystemSculpt

Check the relevant path first

For native chat, check CLI installation/login and Detect again. For hosted work, check Account connection/credits and the exact error. For Similar Notes, inspect Knowledge status/exclusions; for audio, identify the failing stage. Troubleshooting has those branches. You do not need to activate a license or rebuild an index for every unrelated problem.

Include enough to reproduce it

• SystemSculpt and Obsidian versions.
• OS/device and whether this is desktop or mobile.
• Selected chat backend and mode, if relevant.
• Steps, expected result and actual result.
• Exact error and report/request ID, when available.
• A diagnostic snapshot if it helps explain the failure.

Use Advanced → Copy diagnostics snapshot → Copy snapshot for the current diagnostic summary. Review it and any screenshot/transcript before sharing. Replace private source content with a small sample that still reproduces the problem when possible. Never send a password, connection code, full license key or any other secret key in a public report.

Account questions

Use your account's Billing page for existing billing controls and Billing and licenses for plugin activation/sync guidance. Published Terms and Refund Policy remain the source for commercial rights; this support page adds no response-time or refund guarantee.