FAQ

Look here first; if nothing fits, open an issue or discussion in the
community.

Download count on a plugin page never moves?

Download counts come from GitHub download stats, refreshed hourly — not a
live counter. Wait an hour after a fresh release.

Plugin install fails?

Check in order:

Is the author's release a stable one? Drafts and prereleases are ignored
by releases/latest — the symptom is version probing failing outright.
Are all three assets present (<id>-<version>.zip, <id>.zip,
manifest.json)? One missing blocks the install.
An integrity-mismatch error means the downloaded bytes don't match the
manifest — retry on another network to rule out proxy tampering.
A pinned entry (tag + sha256) erroring means the bytes don't match the
pinned hash — ask the author to confirm.

App won't open / blank window?

Confirm the installer matches your system (an Intel build on Apple Silicon
or vice versa may never start) — every download card labels its arch.
An unsigned-build block is not a bug; follow the allow-list steps in
Getting started.
Offline never breaks local features, but the marketplace, version probing,
and model requests all need the network — check connectivity first.

Sign-in / email trouble?

See the last section of Account & sign-in: spam
folder, rate-limit waits, expired links.

Model task fails?

Read the provider's verbatim error first: 401/403 → check key and credit;
429 → lower concurrency and wait.
Then check routing: does the current task have any enabled model? See
Models & providers.
For local models (Ollama-style), confirm the local server is running and
the address is right.

Any Windows vs macOS differences?

Three: the unsigned allow-list location differs, deep-link protocol
registration differs (installers write it in production; dev builds register
manually), and path separators differ (only plugin authors care). No
functional differences.