Skip to content

Commit a1fff51

Browse files
t3dotggclaude
andcommitted
docs(user): server updates are offered from the sidebar and Environments settings, not the conversation
Co-Authored-By: Claude Opus 5.5 <[email protected]>
1 parent 4c8a75c commit a1fff51

1 file changed

Lines changed: 4 additions & 5 deletions

File tree

‎docs/user/updating.md‎

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,8 @@
11
# Updating T3 Code
22

33
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, an update notice appears in the
5-
conversation and **Settings → Environments**. Update the machine named in that
6-
notice.
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.
76

87
## Update everything at once
98

@@ -25,8 +24,8 @@ restarts.
2524

2625
Server updates appear only after that version is published to npm. Remote
2726
desktop apps do not wait for npm. The confirmation lists each machine it skips
28-
and why, such as a machine that is offline or needs a manual update. Use the
29-
notice or **Settings → Environments** for those.
27+
and why, such as a machine that is offline or needs a manual update. Use
28+
**Settings → Environments** for those.
3029

3130
If a desktop app restarts on its old version, T3 Code tells you the update did
3231
not apply. It does not install that version again on its own, even when another

0 commit comments

Comments
 (0)