A component download failed
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.
Repair is running longer than expected
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.
macOS computer use is blocked
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.
The local service or sidecar is unhealthy
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.
A model connection is not ready
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.
A workspace file is not syncing
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.
A package installation failed
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.
Git authentication or merge failed
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.
A background job appears stuck
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.
A chat seems missing
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.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.Contact support
Send the diagnostic details above without secrets.