Desktop operations include updates, licensing, and support recovery.
Polystro has explicit support surfaces for update checks, release notes, bug reporting, and license recovery. Those flows matter because the app owns local repos, services, and agent execution on your machine, so account and runtime health cannot be treated as an afterthought.
Desktop Updates
The desktop app includes a built-in update dialog rather than pushing update management into a separate installer flow. It can show the current version, the latest available version, release notes, download progress, and whether the update is ready to install.
When an update is available, you can update immediately, ask the app to remind you later, or skip that version and keep working.
Manual Checks and Install
Manual check
Open the update dialog from Settings to force a fresh check when you want to confirm the desktop runtime is current.
Release notes
Review the shipped notes before installing so you know whether a change affects your normal workflow.
Download state
The dialog reports whether the update is available, downloading, ready to install, or failed.
Restart and install
Once the update is ready, the desktop can restart into the install flow without making you recreate workstreams.
Bug Reports
Bug reporting is built into the desktop app. When you open the report flow, Polystro collects system information, recent logs, and trace IDs before you submit the issue description.
This is important because many real desktop issues depend on runtime state. A useful bug report often needs the environment around the failure, not just a short sentence saying something broke.
License States
The desktop license gate handles more than first-run activation. It also has explicit recovery states for expired licenses, revoked or suspended licenses, invalid keys, verification failures, and device limit exhaustion.
Expired
Renew from your account, then return to the desktop app and continue with the same local setup.
Device limit reached
Use your account to manage devices when the license is already active elsewhere.
Invalid or verification failed
Check the key and your network first, then retry activation before assuming the local app is corrupt.
Revoked or suspended
If the license is suspended, contact support rather than repeatedly retrying local activation.
Recover From Device Limit
Stop retrying local activation
If the desktop says the device limit is reached, repeated key entry will not fix it because the limit is enforced at the account level.
Open your account device management
Use the account flow to see which device is currently holding the license allocation.
Move or free the allocation
Remove the old device or switch the license to the current machine, then return to the desktop app.
Retry the desktop flow once
After the account state is correct, retry activation from the desktop and continue with the same local workstreams.
Account and Support
Your account is where you buy or renew a license and manage device allocation. Support is the escalation path for suspended licenses, activation issues that survive retry, or bugs that are hard to reproduce without logs.
Practical rule
Return to installation
Review first-run setup, platform notes, and the initial license activation path.
Debug runtime issues first
Use the environment and routing surfaces before escalating preview or service failures as support issues.
Route the issue by symptom
Use the troubleshooting index when you are unsure whether the problem is account-level or a local runtime problem.