Why the platforms should not be merged
Windows users hit SmartScreen and code signing questions more often. macOS surfaces Gatekeeper prompts and automation permissions. Linux varies by distro packaging, libc, and service layout. A single generic page tempts readers to skip the step that actually matters on their machine.
The download status guide keeps the same rule: commands only appear when a current verified source supports them. Otherwise the page points to where to read, not how to blindly run.
Windows: start with provenance and signing
- Where the installer came from and whether filenames match the current release notes.
- Unsigned or unknown publisher warnings: stop and verify the publisher path, not random repacks.
- Corporate networks or endpoint tools blocking downloads: treat that as its own failure mode.
- Model traffic: Windows firewalls and proxies may block API calls separately from install success.
macOS: a permission prompt is not always a broken build
- Confirm you opened the package referenced by the current release page, not a forwarded DMG from chat.
- Read what the app asks to automate before granting broad permissions.
- Strict local network or security tools can break model calls even when the app launches.
- Apple Silicon vs Intel binaries still matter—trust the release labeling.
Linux: write the distro facts down first
- Record distro, version, and whether you use vendor packages, containers, or source workflows.
- Mismatched libc or dependencies often look like random crashes until you reconcile versions.
- Port clashes and systemd user units show up more on servers than on casual desktops.
- If you run under a low-privilege account, validate secret storage and file mounts separately.
Cross-check model quota and post-update issues
Finishing setup is only step one. For quota messages or “broken after update,” see quota and post-update notes plus the connection troubleshooting guide so you do not reinstall twice for two different problems.
Platform download FAQs
Should Windows, macOS, and Linux install steps be treated the same?
No. Permission models, signature expectations, and packaging habits differ. This site does not publish a universal command list. Use the current download page and verifiable release notes, then keep your own checklist for your OS.
Should I verify a build number before installing?
Yes, but do not trust random screenshots. Match what the current release page and checksum notes say. The download page keeps a verification tone rather than promising unconfirmed version details.
Is it safe to copy commands from random tutorials?
Be careful. Tutorials often lag releases. Unknown scripts make troubleshooting harder. Prefer verified sources and minimal-permission validation on your machine when needed.
Return to the download page for your OS
Verify sources and platform differences before committing to a personal AI assistant setup.
Open download page Download status guide