|
Three install methods, three update paths. Pick yours. |
Answered by
Ark0N
Aug 15, 2026
Replies: 1 comment
|
Depends on how you installed:
No hard refresh needed afterwards; assets are cache-busted automatically. The one known exception is iOS Safari, which sometimes clings to old JS until you fully close the tab (not just switch away) and reopen it. Release notes for every version are on the releases page, and each one credits the people who reported and fixed things. |
0 replies
Answer selected by
Ark0N
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Depends on how you installed:
install.sh): use the in-app updater (App Settings, System, Updates). It pulls, builds, and restarts the service, and the progress survives the restart. Re-running the installer script withupdatedoes the same from the shell.npm install -g aicodeman@latestgit pull && npm install && npm run build, then restart however you run it.No hard refresh needed afterwards; assets are cache-busted automatically. The one known exception is iOS Safari, which sometimes clings to old JS until you fully close the tab (not just switch away) and reopen it.
Release notes for every version are on the releases page, and each one credits the people w…