Start
Install the correct build and keep local data protected.
Gimmer publishes separate Windows, macOS, and Linux assets. Always obtain the installer from the official download page or public release repository.
Choose the platform package
| Platform | Use | Before opening |
|---|---|---|
| Windows | The current Windows setup executable. | Confirm the publisher source and preserve any warning text if the operating system blocks launch. |
| macOS | The current macOS application archive or package. | Move the app to Applications and follow macOS security prompts for the downloaded build. |
| Linux DEB | The 64-bit package for Debian, Ubuntu, and compatible distributions. | Install with your system package manager so declared GTK and WebKit dependencies are resolved. |
| Linux RPM | The 64-bit package for Fedora, RHEL, Rocky Linux, and compatible distributions. | Install with your system package manager so declared GTK and WebKit dependencies are resolved. |
Install without replacing local data
- Close active work deliberately. Confirm the state of live or simulated strategies before stopping the app.
- Back up first. Keep a current recovery copy before an operating-system change, manual data move, or repair installation.
- Run the package for your platform. Do not copy a Windows executable to Linux or use the macOS asset on another operating system.
- Launch and verify. Confirm that the version shown in the app matches the release and that strategies, connections, positions, and activity are present.
Update the app
When Gimmer detects a newer public release, the app can offer an update beside the current version. Save work, allow the download to finish, and let the app restart. The updater selects the package for the current operating system.
If the in-app update is unavailable or the app cannot open, install the latest public package over the existing application only after making a backup. Do not delete local data directories as a first troubleshooting step.
Protect state before repair
The executable and your local operating data are different concerns. Replacing the app binary should not require erasing strategies, history, wallets, or runtime records.
Troubleshoot launch problems
- Restart the operating system after a locked-file or pending-update failure.
- Confirm that endpoint security did not quarantine the executable.
- Check that the installed build matches the operating system and architecture.
- Capture the exact launch error and app version before reinstalling.
- Use Support before deleting local application data.