The best way to control Claude Code, Codex and more from any computer or phone

main
md 214 lines 11.2 KB
Rendered Raw
1 # Updating T3 Code
2
3 The app you use and the server running your agents can be on different machines.
4 When a server is behind your web or desktop app, the update button at the bottom
5 of the sidebar and **Settings → Environments** offer to update it.
6
7 ## Update everything at once
8
9 The update button at the bottom of the sidebar updates every connected machine
10 in one step. It updates outdated providers, then servers that are behind, then
11 the desktop app you are using. Servers move to the
12 version your desktop app is installing, or to your web app's version. A
13 background service stays on its current release channel. A remote desktop app
14 installs the latest release from its own channel. Hover the button to see what
15 it will update.
16
17 While it runs, the button widens to show progress. It names a machine that is
18 taking longer than usual, and offers **Retry** for a server that failed. Click
19 it to see every machine. The desktop app restarts once each server has started
20 its own restart, after a short countdown. Choose **Later** to keep working and
21 restart from the update button when you are ready. A server still restarting
22 finishes on its own, and the button keeps showing it after the desktop app
23 restarts.
24
25 Each server checks that it can install the release before it restarts. If the
26 release is not available to a server yet, its update fails, the server keeps
27 running, and you can retry. The confirmation lists each machine it skips and
28 why, such as a machine that is offline or needs a manual update. Use
29 **Settings → Environments** for those.
30
31 If a desktop app restarts on its old version, T3 Code tells you the update did
32 not apply. It does not install that version again on its own, even when another
33 device asks. Use the update button on that machine to retry.
34
35 The confirmation counts the running threads that the restarts will interrupt,
36 and how many can resume afterwards. See **Continue threads after restarts**
37 below.
38
39 ## Switch between Stable and Nightly
40
41 In the desktop app, change **Settings → About → Update track**. T3 Code shows each
42 connected machine it will move and each one it skips, then moves them in one
43 step. Remote servers install the latest release on the new track. Remote desktop
44 apps reinstall on the new track. This app reinstalls last. Your threads,
45 settings, and data stay.
46
47 A background service cannot move to an older release remotely. When Stable is
48 older than its Nightly, run `t3 update --channel stable --allow-downgrade` on
49 that machine.
50
51 A switch is blocked for a machine whose database already has changes the
52 target release does not support, or when T3 Code cannot confirm that it does.
53 The dialog says why: update a machine on its current track first when its
54 release is too old to check, or wait until the target track includes the
55 changes. A Mac running the desktop app must switch on that Mac.
56
57 Each machine keeps the new track even if its switch did not finish, but it
58 moves to that track only through a switch. **Update track** shows how many
59 machines still run the other track. **Review** opens the same dialog with fresh
60 checks.
61
62 ## Before you update
63
64 Server updates restart the connection and can interrupt active agents and
65 terminal commands. Saved threads, settings, and project files remain.
66
67 **Settings → Maintenance → Continue threads after restarts** is on by default.
68 It resumes supported active threads after an update, crash, or machine
69 restart. Changes are saved to connected environments that support this setting;
70 update older servers first. If a supported environment was offline or has a
71 different value, use **Apply to all** in Settings after it connects.
72 T3 Code must start again on that machine;
73 the setting does not enable automatic startup. Terminal commands may still be
74 interrupted, and threads without saved provider resume state need a new message.
75 A thread that finished its turn to wait on a subagent, a background task, a Claude
76 monitor, or a command or other monitor the agent said it was waiting on is woken and told that this work
77 stopped. Other background shells and monitors, such as a dev server and its
78 watchdog, do not wake it; the thread learns about them with your next message.
79 A thread is not resumed while it waits for your approval, answer, or secret, or
80 while it is archived, snoozed, or settled. After three consecutive crash recoveries
81 of an unfinished turn, the thread waits for your next message, even when crashes
82 are more than five minutes apart. A completed turn or a planned shutdown resets
83 that limit.
84
85 Updates from the previous orchestration system preserve conversation transcripts but cannot carry
86 every kind of runtime history forward. Read [Threads from older T3 Code versions](./thread-migration.md)
87 before continuing an important older thread.
88
89 ## When versions don't match
90
91 A client and server must speak the same orchestration protocol. If they do not, the connection is
92 refused rather than running half-upgraded:
93
94 - An app newer than the server is blocked before connecting, with a notice telling you to update
95 T3 Code on the machine named in the notice.
96 - A server newer than your app refuses the connection with an update message.
97
98 Update the side the notice names, then reconnect.
99
100 ## Update a connected server
101
102 The offered action depends on how the server runs:
103
104 | Action | What to do |
105 | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
106 | **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. |
107 | **Update the desktop app** | Update the desktop app on the machine running the server, then reopen it if needed. |
108 | **Copy update command** | Run the command on the named host to update the detected global npm install or installed `t3` command, then restart the server with your usual options. |
109 | **Copy relaunch command** | Stop the command-line server on its host and relaunch with the copied command, keeping your usual subcommand and options. This does not update an installed `t3` command. |
110
111 On the host, run:
112
113 ```sh
114 t3 update <client-version>
115 ```
116
117 Replace `<client-version>` with the version shown in the notice. The command
118 asks before restarting the background service; if you decline, run
119 `t3 service restart` when you are ready. For a server you started by hand,
120 stop it and start it again afterwards with your usual options such as `--host`
121 or `--tailscale-serve`.
122
123 If you decline the restart for a background service installed by an older
124 release, the service can stay down after a crash or reboot until you run
125 `t3 service restart`.
126
127 If you run the server with `npx` rather than an installed `t3`, there is
128 nothing to update on the host: stop the server and relaunch it as
129 `npx t3@<client-version>` with the same subcommand and options.
130
131 ## If an update fails
132
133 Keep the client open until it reconnects or reports a failure. A failed service
134 update can roll back to the previous version. If the update still fails:
135
136 1. Retry the offered action once.
137 2. Check that you updated the server's machine, not only the device you are using.
138 3. For a command-line server, stop it and relaunch the exact version shown in the notice.
139
140 Only one server can use a T3 home directory at a time. If startup reports that
141 another server owns it, stop that server before retrying, or use a separate home
142 directory and pair with the running server.
143
144 ### macOS app does not reopen after an Alpha update
145
146 Updating an older **T3 Code (Alpha)** installation can replace it with
147 **T3 Code (Beta)** without reopening the app. Open **T3 Code (Beta)** from
148 Applications, or run:
149
150 ```sh
151 open "/Applications/T3 Code (Beta).app"
152 ```
153
154 If an old Dock shortcut no longer opens the app, remove it and add the Beta app
155 from Applications again.
156
157 ## If the desktop app does not start
158
159 If the desktop app's server keeps failing at startup, T3 Code shows a "T3 Code
160 could not start" window instead of the app. If a newer version is available,
161 choose **Update** to install it. If not, the window links to the last version
162 that started on your computer. Download and install it to go back. Use **Copy
163 details** to include the error in a bug report.
164
165 ## Registries and proxies
166
167 Each server checks T3 Code releases, and providers installed with npm, through
168 its own npm, so the checks use npm's configured registry, authentication, and
169 proxy settings. Providers installed with Homebrew or pnpm check through those
170 tools.
171 Configure npm on the server's machine. If that registry cannot be reached, the
172 release shows as unavailable; T3 Code does not try the public registry instead.
173 Machines without npm check the public npm registry directly.
174
175 ## Update providers
176
177 **Settings → Providers** shows provider updates for the selected environment.
178 **Update all** updates every outdated provider on every connected environment
179 at once. Hover it to see which providers it will update. A provider is left out
180 when any of its enabled, outdated instances offers only a manual update command,
181 or when its instances use different update commands, such as two instances that
182 run different CLI installs. Update those by hand, or point every instance of the
183 provider at the same CLI.
184
185 After a successful provider CLI update, T3 Code refreshes model discovery for
186 every enabled instance of that provider using its own configuration. Connected
187 clients receive the refreshed catalogs automatically. Provider update checks
188 must be enabled to download the latest T3 Code model catalog.
189
190 Provider updates do not restart running chats. An existing session can keep
191 using the previous CLI until it ends. If discovery fails, check the provider
192 status and refresh it again.
193
194 ## Mobile updates
195
196 To update an environment from your phone, open **Settings → Environments** and
197 select it. **Check for updates** finds the latest release on that environment's
198 current release channel. Keep the app open while the environment updates and
199 reconnects. Hosts that cannot update remotely show instructions for updating on
200 the machine instead.
201
202 The same page lets you refresh provider status and update supported providers.
203 These controls require a connected environment and permission to operate it.
204 Provider update checks and restart continuation preferences are in
205 **Settings → Maintenance**. If provider update checks are disabled, enable them
206 there before refreshing to find newer versions. The same setting controls whether
207 T3 Code downloads model catalog updates, so with it off new models may not appear
208 until you enable it and refresh provider status.
209
210 Install App Store or Google Play releases as usual. The mobile app can also
211 download updates in the background and apply them when you next leave the app.
212 It saves drafts and queued messages before restarting. If you keep the app open
213 for a long time, it may ask to install immediately; choosing **Later** leaves the
214 update queued for the next suitable moment.