Personal Jarvis has a new name: Dodaios. The website is now dodaios.ai, and the source code is at github.com/Dodaios/Dodaios. It is the same app, built by the same people, under the same Apache 2.0 licence.
If you already have the app installed, one thing needs doing by hand: update it once. Versions up to and including 3.1.1 can no longer see new releases, and the reason is a single redirect that our update check does not follow. Your settings, API keys and data stay where they are.
This post covers what changed, what did not, the one manual update, and three things the move broke on our side. “We” means the people building Dodaios and the coding agents that do much of the typing. The grey chips like update_routes.py link to the source on GitHub.
What changed
| Before | Now | |
|---|---|---|
| Name | Personal Jarvis | Dodaios |
| Website | personaljarvis.ai | dodaios.ai |
| Blog | personaljarvis.ai/blog | dodaios.ai/blog |
| Source code | github.com/PersonalJarvis/PersonalJarvis | github.com/Dodaios/Dodaios |
| Logo | A ghost | A small hooded figure |
You also find us at x.com/dodaios and youtube.com/@Dodaios. The Discord invite is the same as before.
Dodaios is the name of the app. It is not a new name for your assistant, which still answers to the wake word you picked during setup.
What did not change
- The app. The same features and the same code. You still need no account.
- The licence. Apache 2.0, free to use.
- Your data. Settings, API keys and everything the app stored stay on your computer.
- The names you type. The command is still
jarvis, the settings file is stilljarvis.toml, the Python package is stillpersonal-jarvis, and the release files are still calledPersonalJarvis-Setup-x64.exeand so on. They work as they are. - Old links. GitHub redirects the old repository address to the new one, for pages, raw files and
gititself. - Earlier posts on this blog. They keep the name they were written with, under a one-line note.
Update once if you already have it installed
The update check in 3.1.1 and older asks GitHub for the latest release of PersonalJarvis/PersonalJarvis. Since the repository moved, GitHub answers that request with a redirect to the new address instead of the release.
The check does not follow redirects, and it treats every answer that is not a release as “nothing new”. So the app stays silent and never offers you the update. The code is _fetch_latest_release in update_routes.py.
The way out is to get past 3.1.1 once, by hand. There are two ways.
Run the install command again
On macOS and Linux, in a terminal:
curl -fsSL https://raw.githubusercontent.com/Dodaios/Dodaios/main/install/install.sh | bash
On Windows, in PowerShell:
irm https://raw.githubusercontent.com/Dodaios/Dodaios/main/install/install.ps1 | iex
The installer finds the existing installation and updates it in place. It does not install a second copy.
Or install a newer download
If you use the desktop installer, download one from the release page. It has to be newer than 3.1.1. The 3.1.1 installer still carries the old check.
Either way, your settings, API keys and data are left alone.
What the move broke on our side
GitHub’s redirects made the rename look safe. Links worked, clones worked, the install command worked. Everything that broke was a place where our own code handled the old name as text.
The update check. That is the one described above, and the only one you have to act on. It was written to fail quietly, so that a network problem never interrupts anybody. The same quiet hid the redirect.
The star map on the website. The globe that shows where the project’s stars come from reads a small public feed. Its sync refuses a feed whose repository name is not the one it expects. On October 11 the feed started to say Dodaios/Dodaios, the website still expected the old name, and every scheduled sync failed from then until we changed the expected name.
This blog’s address. The blog is published from its own repository and borrows the website’s domain. GitHub Pages lends an organisation’s domain to its other repositories only while the website lives in a repository named after the organisation. We renamed that repository, and on October 12 personaljarvis.ai/blog answered 404.
Two of the three were built to fail quietly. The update check says nothing when GitHub does not answer with a release, and the star map keeps its last good picture when a feed looks wrong. Both did exactly that.
A redirect covers a link. It does not cover a comparison. If you move a repository of your own, search your code for the old name as a string before the move: update checks, feed validators, allow-lists, hosting rules that depend on a repository’s name.
What to take from this
- Installed already? Update once, with the install command above or an installer newer than 3.1.1.
- Change your bookmarks to dodaios.ai. The blog’s feed is now
https://dodaios.ai/blog/rss.xml. - Point scripts and
gitremotes atDodaios/Dodaios. The old address redirects, but it is no longer the real one. - Renaming something yourself? Search for the old name as a string first, and look hardest at the code that fails quietly.
If something stopped working for you after the rename, tell us in an issue and say which version you came from.
What we checked. On October 12, 2026 we requested the old repository address as a web page, as a raw file and with git ls-remote, and all three reached the new repository. On the same day GitHub’s API answered a request for the latest release under the old name with HTTP 301. The update check described here is the one in the 3.1.1 release. The failed syncs are the scheduled runs in the website repository’s Actions history from October 11. This post does not announce a new release.