> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ospribrain.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Diagnose release availability, setup, permissions, services, connections, sync, packages, Git, and jobs.

Start with **Setup** on Home. Required and optional diagnostics are listed separately.

<AccordionGroup>
  <Accordion title="The runtime manifest is unavailable">
    Full Workstation is release-gated. If `downloads.ospribrain.com` returns an unavailable-artifact error, confirm that the signed release has actually been published for your channel. Do not substitute a different platform's archive.
  </Accordion>

  <Accordion title="A component download failed">
    Retry Setup after checking network, proxy, firewall, disk, and CDN access. Completed verified components are preserved. An incomplete archive is deleted and downloaded again rather than resumed from arbitrary partial bytes.
  </Accordion>

  <Accordion title="Repair is running longer than expected">
    Repair performs a fresh full-profile install and requests every selected component archive before switching the active runtime. It is not currently a damaged-file-only download.
  </Accordion>

  <Accordion title="macOS computer use is blocked">
    Return to Permissions. Approve Accessibility and Screen Recording through the normal macOS prompts, then recheck. Windows does not use these macOS prompts.
  </Accordion>

  <Accordion title="The local service or sidecar is unhealthy">
    Restart the app once, reopen Setup, and rerun the final check. Record the exact failing diagnostic. If it remains unhealthy, contact support with the app version, operating system, processor, and error text.
  </Accordion>

  <Accordion title="A model connection is not ready">
    Open Connections and verify the provider credential, endpoint, model configuration, and provider account limits. Return to Setup and run the model check again. Never include the credential value in a support message.
  </Accordion>

  <Accordion title="A workspace file is not syncing">
    Open Files and inspect the workspace status shown on Home. Confirm the file is inside the OSPRI Science workspace and record any visible sync error. Files inside a separate coding-project folder follow that project's local workflow.
  </Accordion>

  <Accordion title="A package installation failed">
    Read the package manager's actual error. Check the lockfile, operating-system wheel or prebuilt binary, Python or Node version, and whether an official vendor compiler is required. Do not blindly switch package versions.
  </Accordion>

  <Accordion title="Git authentication or merge failed">
    Inspect repository status and the current branch before retrying. OSPRI has no in-app Git credential connector. Resolve conflicts and authentication through the repository's configured Git method.
  </Accordion>

  <Accordion title="A background job appears stuck">
    Open Generations for cloud agent runs. Open the linked chat or cancel a queued or running job. Local Deep builds are tracked in the Code panel instead.
  </Accordion>

  <Accordion title="A chat seems missing">
    Home shows only ten recent chat cards. Use `⌘K` on Mac or `Ctrl+K` on Windows to search older and unfiled chats.
  </Accordion>
</AccordionGroup>

## Windows on ARM

Windows on ARM is intentionally blocked because required upstream binaries and wheels are incomplete. Do not rename x64 runtime or installer files as ARM files.

## App updates and removal

Use only the product-isolated OSPRI Science update channel. The renderer does not currently expose an in-app managed-runtime uninstall or cleanup control. Remove the app through the normal operating-system process. Contact support before manually deleting runtime data so work files are not removed by mistake.

## Information to send support

Include the OSPRI Science version, operating system, processor, failed setup step, exact visible error, and what changed after retry or restart. Do not include API keys, passwords, tokens, or credential files.

<Card title="Contact support" icon="envelope" href="mailto:support@ospri.com">
  Send the diagnostic details above without secrets.
</Card>