Update Rudr

Choose the update flow your installation supports

Qualified macOS builds can download and install an update inside Rudr. Older unsigned or manual-update builds need a one-time DMG installation of a qualified signed build to gain that capability. Windows continues to use a manual installer. Changing release metadata cannot add new update features to an older installed app.

Check the actual public release notes and installers for availability and qualification. These instructions do not assign a future version or claim that a particular signed update has shipped.

Update a qualified Mac installation

1. Open Settings → Updates, or choose Check for Updates from Rudr's application or menu-bar menu. Review Current version and choose Check for updates when needed.
2. Read What's new or choose View release notes. Automatically check for updates controls checks only; downloads and installation always wait for you.
3. Choose Download update. Rudr shows progress and verifies the downloaded app before making installation available. Downloading does not replace the running app.
4. Choose Later to continue working, or Restart and install when ready. Ordinary Quit does not install a downloaded update. Opening Updates or checking for a release does not install it either.
5. Review the final confirmation about active work. Rudr prepares saved drafts and layout state, then stops active work before handing off installation. If it names a blocker, resolve it and retry.
6. After relaunch, check Current version. The update is only reported complete when the running version and verified app identity match the install receipt. A failed or interrupted restart is not reported as success merely because a download finished.

Save or resolve unsaved Settings and API-key fields, temporary side chats, queued prompt edits, and Git commit/PR work before restarting. Finish dictation or image generation and allow draft recovery to finish. Rudr blocks restart when these cannot be safely preserved. Review active chats, Code runs, terminals, and browser work before consenting to stop them; external unsaved work still needs your attention.

Install the one-time Mac upgrade or a Windows update

If Download update opens your browser, your installation uses the manual path. Builds without a working checker can use the website or public releases page directly. A downloaded installer does not install itself.

1. Choose the matching installer and read its release notes. GitHub's Source code archives are not installers.
2. Finish active runs, save files and drafts, and quit Rudr.
3. On macOS, open the DMG, drag Rudr into Applications, and replace the existing copy. Eject the DMG and reopen Rudr from Applications. Use the qualified release's expected Developer ID identity; follow an ordinary first-open Gatekeeper confirmation. If macOS reports an unidentified developer, a damaged app, or an unexpected signer, stop and check the release rather than removing quarantine or disabling Gatekeeper.
4. On Windows, run the available matching installer and follow its prompts, then reopen Rudr. A missing Windows installer cannot be replaced with a Mac asset.
5. Confirm the installed version in Settings → Updates, then check sessions, drafts, settings, and provider configuration.

Do not delete Rudr's app-data folders to update. History, settings, saved drafts, projects/worktree associations, and browser state are stored separately from the replaceable application. Preservation is tested for each qualified release. First signed installation or an update may prompt for Keychain access or macOS permissions; prompt-free provider authentication and permission continuity are not promised until tested for that release. An unexpected credential problem belongs in support diagnostics, not a request to share passwords or keys.

Understand check and recovery states

• Up to date: the latest compatible version matches this installation.
• Ahead: this installation is newer than the published version; Rudr does not offer a downgrade.
• No release / incompatible: there is no eligible release for the installed app architecture or macOS version. An Intel app running under Rosetta stays on its x64 update path. Do not choose a different architecture to bypass a failed compatibility check.
• Couldn't check / offline: continue working and retry when connected. A last-checked timestamp or retained offer may be from an earlier successful check; it is not freshly verified availability. Checks can briefly reuse a recent result to avoid repeated requests.
• Download or verification failed: use Try again when available, then explicitly download again. Do not install a file whose verification failed or bypass macOS security checks.
• Preparation or restart failed: resolve the named blocker and check the running version before trying again. If installation has already been handed to macOS and takes longer than expected, Rudr must not pretend that it has canceled or completed. Preserve the displayed error for support.
• Unavailable: development builds or unsupported platforms cannot use this update path.

Checks and downloads need a connection but no GitHub account. For support, record the current/offered version, Mac/Windows version, app architecture, last-check time, and displayed error. Never include API keys or provider auth files. See installation, release notes, and Diagnostics.