Troubleshoot SystemSculpt

Claude Code or Codex is unavailable

Check that the selected CLI is installed and signed in on the same desktop computer. Confirm it runs outside Obsidian, then use Detect again in the chat backend menu. A SystemSculpt license is not the fix for a missing native CLI. On mobile, saved native chats are readable but the desktop backend cannot run there.

SystemSculpt looks for claude and codex on the PATH and in common install folders, including Homebrew, npm, nvm, Volta, asdf, fnm, bun and pnpm. If yours is elsewhere, set its path as binary in ~/.config/systemsculpt/claude.json or codex.json, then choose Detect again. Sign-in status unknown means the sign-in check was slow, not that you are signed out.

Claude Code or Codex reached its usage limit

The chat shows Claude Code usage limit reached or Codex usage limit reached, with the reset time when the agent gives one. Use SystemSculpt instead starts a new hosted chat, which uses account access and credits, and keeps the original chat in history. Nothing is sent to SystemSculpt until you choose it; new chats then use SystemSculpt until you pick another backend.

Hosted chat or sign-in fails

Check Account connection and credits, then read the exact request error. If browser return fails, use Open the sign-in page again, paste the Connection code, then Complete sign-in. If email verification is requested, complete that step before retrying. Do not repeatedly purchase or reactivate a license to solve an unrelated service error. If chat rejects your license, the failed message offers See plans; when you are out of credits it offers Add credits, or See plans if you have no plan.

Similar Notes is missing expected results

Check Knowledge → Similar notes, exclusions and Index status. Use Refresh status and View remaining files to see whether indexing is unfinished. Check whether the expected note is excluded. Rebuild only when repair is warranted; ordinary edits are not a reason for a full reset. See Semantic search.

Audio will not record, import or transcribe

Identify which stage failed: recorder, device-file import, standard transcription or Audio Processor. Check microphone/Workflow settings for capture, and supported format/size for the exact input path. The limits differ by operation and older host version; use the audio limit table, not a universal mobile number. Stop a recording and wait for Recording saved before suspending the app. If you chose Not now when several audio files arrived at once, nothing was sent; run Resume inbox transcription when you are ready.

Save diagnostic information

If a failed SystemSculpt chat message offers a report, wait through Preparing report… for Copy report ID. Report unavailable → Retry report retries saving the diagnostic report, not the failed model turn. You can also use Advanced → Copy diagnostics snapshot → Copy snapshot. Record diagnostics is normally off; do not leave extra collection on just because you visited this guide.

Send the report/request ID, versions, OS/device, backend/mode and reproduction steps through Support. Review/redact anything you attach. Do not publish credentials, license keys or private notes.