Search documentation

Find guides and API references.

Documentation

Support playbook

Prep accurate diagnostics before you file a ticket. The tooling below mirrors the support triage workflow.

Before you contact support

Run through this checklist to capture environment info, logs, and reproduction details. Each step maps to a specific command or service inside the plugin so you can verify it on your side.

Step 1
Capture environment details
Open Settings → SystemSculpt → Quick actions and click the feedback link. It prepares a draft with your plugin version, Obsidian build, operating system, and enabled providers.
Step 2
Validate license & provider connectivity
Click “Activate” in Settings → Overview & Setup (or “Test connection” on a custom provider) to confirm your license or API key is accepted before you escalate.
Step 3
Export runtime logs
Use Export SystemSculpt Error Logs from the command palette so you can attach the generated text file to your ticket.
Step 4
Attach a reproduction transcript
From the affected chat, run Export chat or Save as Note so support can see the full conversation, prompt, and attachments.
Step 5
Run Janitor diagnostics
Open the Janitor modal from the command palette to retry stuck processing jobs and log the results.

Where to file

Pick the channel that matches the severity of your issue. Email and the contact form fan out to the primary support queue; GitHub Issues is best for tracked bugs and feature requests.

Email support
Send incidents to support@SystemSculpt.com with exported error logs and a copy of your manifest.json version block.
GitHub Issues
Report bugs and request features at github.com/SystemSculpt/obsidian-systemsculpt-ai/issues — the central tracker for release follow-ups and support.
Contact form
Use the /contact route to file prioritized tickets; the serverless handler fans out to the support queue and Slack alerts.
TipInclude exported logs, your plugin version, and any chat transcripts when opening a ticket so engineering can replay the scenario immediately.

Diagnostics you already have

These utilities surface the same internal state used during debugging. Run them after you collect logs to double-check processing queues and agent permissions.

Janitor modal
Shows stuck document processing jobs, lets you retry them, and clears leftover temporary files.
Error logger
Collects plugin notices in one place. Use the “Export SystemSculpt Error Logs” command to share a text copy.
Freeze monitor & watchdogs
Background watchdogs that warn you about stalled queues or outdated builds.
Resume chat service
Reads the metadata stored in chat history files so you can relaunch a conversation with its saved model and context.

Need more guidance? Review the troubleshooting procedures or scan the FAQ for policy questions before escalating.

Previous

FAQ