Skip to content

updating.md

Latest commit

 

History

History
58 lines (42 loc) · 3.18 KB

updating.md

File metadata and controls

58 lines (42 loc) · 3.18 KB
Raw

Updating T3 Code

The app you use and the server running your agents can be on different machines. When a server is behind your web or desktop app, an update notice appears in the conversation and Settings → Connections. Update the machine named in that notice.

Before you update

Server updates restart the connection and can interrupt active agents and terminal commands. Saved threads, settings, and project files remain.

Settings → General → Continue threads after server updates is off by default. Enable it to resume supported active threads once the replacement server is ready. Terminal commands may still be interrupted.

Update a connected server

The offered action depends on how the server runs:

Action What to do
Update server Keep the client open while it installs and reconnects. Supported background services update remotely. For a desktop-hosted server, this also closes and relaunches the desktop app on the host.
Update the desktop app Update the desktop app on the machine running the server, then reopen it if needed.
Copy update command Stop the command-line server on its host and relaunch with the copied command, keeping your usual startup options.

For a background service, run the matching version's CLI on the host:

npx t3@<client-version> service update

Replace <client-version> with the version shown in the notice. Using @latest only resolves the mismatch if your client is on that release. An older service launcher may require this local update before it supports remote updates and rollback.

For a foreground server, the copied command is npx t3@<client-version>. Add serve if you normally run without a browser, and preserve options such as --host or --tailscale-serve. See background services for service management.

If an update fails

Keep the client open until it reconnects or reports a failure. A failed service update can roll back to the previous version. If the update still fails:

  1. Retry the offered action once.
  2. Check that you updated the server's machine, not only the device you are using.
  3. For a command-line server, stop it and relaunch the exact version shown in the notice.

Mobile updates

Install App Store or Google Play releases as usual. The mobile app can also download updates in the background and apply them when you next leave the app. It saves drafts and queued messages before restarting. If you keep the app open for a long time, it may ask to install immediately; choosing Later leaves the update queued for the next suitable moment.