Updates and versions
How 9xchat updates, why a new build often fixes a model or tool problem, and what to include in a report.
Models, providers, and tools change on their own schedule, and the code that talks to them ships inside the build. Checking your version is the cheapest first step.
Check your version
The version is printed at the bottom of the left sidebar, under the icons — for example v2.0.2. Quote it in any support message.
How updates arrive
- Desktop builds update themselves. When one is ready the app tells you; restart it to finish.
- Microsoft Store builds update through the Store with your other apps.
- Android and iOS builds update through Google Play and the App Store.
You can always fetch the current build by hand from the download page, which is the source of truth for what is released.
When to update before anything else
- A model that used to work has disappeared from the list, or stopped responding. Provider APIs change, and the model catalogue ships with the app.
- A tool or MCP server broke after working.
- A screen does not match this documentation. These pages follow the current release, so an older build can differ.
What changed in each build
Release notes for every version are published at 123sudo.com/changelog/9xchat.
Before you report a problem
Update, retry, and then work through Troubleshooting. If it persists, send support your operating system, the 9xchat version, the model and provider, and the exact visible error.
Never include your UID, an API key, MCP secrets, or private conversation contents in a report or screenshot.