Updates
askTheodor keeps itself current. It checks the official site for a newer signed release, downloads and verifies it, then restarts into the new version — your workspace and settings carried over untouched. This tab is the manual surface: check on demand, read what changed, and install when one’s ready.
A quiet background check also runs on launch with a gentle “update ready” nudge; this is where you drive it explicitly.
Installed version
A panel shows your current installed version (e.g. v0.9.149) and a Check for updates button.
Check for updates
Click Check for updates. One of three things happens:
- ✓ You’re on the latest version — nothing to do.
- Update available — a highlighted card appears with the new version number, its release date, and the changelog (what changed). From here you can install.
- ⚠ Couldn’t check for updates — the update service wasn’t reachable. The panel explains the situation and offers an Open download page button so you can always grab the latest build from the website manually.
Install an update
In the update card, click Download & install, then restart. askTheodor downloads the release, verifies its signature, installs it, and relaunches into the new version. While it works you’ll see a progress bar (Downloading… → Installing…), and when it’s done the app restarts on its own.
In practice
Check the version here before reporting a problem. askTheodor ships often, and a good share of “this is broken” turns out to be a bug already fixed in a later build. The installed version on this panel is the first thing worth knowing — quote it in any bug report.
Updating never touches your workspace. The update replaces the application binary only; Companies, workers, routines, conversations, Library, providers and license all stay exactly where they are. There’s no migration step for you to run and nothing to re-enter afterwards.
Signature verification is what makes an auto-updater safe. Every release is signed, and the app checks that signature before installing — a tampered or substituted download is rejected rather than executed. That’s why “couldn’t check for updates” is the correct behaviour when something’s off, rather than installing anyway.
“Couldn’t check for updates” is usually the network, not the release. A firewall, an offline machine, or a VPN blocking the update host all produce it. Use Open download page to install by hand — a failed check leaves your current install untouched.
Update before a long unattended run. If you’re about to leave routines or a Team-Hub working overnight, take the update first. Restarting into a new version mid-run interrupts work in progress.
Terms in this page
- Version — the release number of the app you’re running (e.g.
v0.9.149). Higher is newer. - Update / release — a newer build of askTheodor published on the official site.
- Changelog — the list of what changed in a release: new features, fixes, and improvements.
- Signed / signature — a cryptographic stamp proving a release genuinely came from askTheodor and wasn’t altered. The app verifies it before installing.
- Tauri updater — the built-in component that downloads, verifies, and installs updates for the desktop app.
- minisign — the small signing scheme used to sign releases and check their authenticity.
- Relaunch / restart — the app closing and reopening itself so the freshly installed version takes effect.
- Background check — an automatic, quiet check for updates that runs when the app launches and nudges you if one is ready.