Documentation

Troubleshooting

Each fix mirrors the guardrails built into the plugin. Follow the steps below before escalating to support.

Rapid fixes

Model picker is empty or returns 401 errors
Re-run “Test connection” in Settings → Overview & Setup and confirm API credentials or license details.

Work through each step in order. Most issues clear up after validating credentials or reprocessing a document.

Transcription stalls at Processing…
Enable automatic audio resampling or switch to the SystemSculpt provider, which chunks uploads automatically.

Work through each step in order. Most issues clear up after validating credentials or reprocessing a document.

Embeddings never finish indexing
Confirm embeddings are enabled, provider credentials are set, and run “Rebuild Embeddings (Current Model)” from the command palette.

Work through each step in order. Most issues clear up after validating credentials or reprocessing a document.

Context files are ignored in responses
Verify the file appears as a chip above the composer. Re-add via drag-and-drop and watch the processing panel for errors.

Work through each step in order. Most issues clear up after validating credentials or reprocessing a document.

Instrumentation you can trust

These utilities run inside the plugin and expose the same state inspection hooks the team uses during QA.

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.

For example, the Janitor modal can retry stuck ingestion stages and logs the results for later export.

Collect logs before you escalate

SystemSculpt keeps an in-memory buffer of notices from features like streaming and licensing. Export a snapshot before contacting support.

Clean Up Phantom MCP Tools
Removes Model Context Protocol entries for servers that are no longer reachable.

Call from: Command palette → Clean Up Phantom MCP Tools

Export SystemSculpt Error Logs
Saves a timestamped error log file into your saved chats folder and opens it for review.

Call from: Command palette → Export SystemSculpt Error Logs

Open Mobile Debugging Guide
Creates or opens docs/mobile-debugging.md, a note with mobile troubleshooting steps.

Call from: Command palette → Open Mobile Debugging Guide

TipAttach the exported log and the affected chat history file when you email [email protected]or post in Discord. Include your plugin version from Settings → Overview & Setup.

Still stuck?

Review the support playbook for escalation paths and response-time expectations, or browse the FAQ for policy questions.