You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7c81f45
Browse filesBrowse the repository at this point in the historyBrowse files
description="Keep this computer available to remote clients by preventing automatic idle sleep while T3 Code runs. The display may turn off; closing a laptop lid can still sleep it."
1725
+
status={
1726
+
preventSleepForRemoteConnections ? null : (
1727
+
<spanclassName="block text-warning">
1728
+
Remote connections can become unavailable when this computer sleeps.
Copy file name to clipboardExpand all lines: docs/user/remote-access.md
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,6 +32,16 @@ That gives you:
32
32
- transport security at the network layer
33
33
- less exposure than opening the server to the public internet
34
34
35
+
## Keeping the Desktop Host Awake
36
+
37
+
In the desktop app, open **Settings** → **Connections** and turn on **Prevent automatic sleep**
38
+
when this computer should remain available to remote clients. T3 Code then holds the operating
39
+
system's native sleep-prevention assertion for as long as the desktop app is running. You do not
40
+
need to run `caffeinate` or change the computer's system sleep schedule.
41
+
42
+
The display can still turn off. Manually choosing Sleep or closing a laptop lid can still put the
43
+
computer to sleep, which makes its T3 Code environment unavailable until the computer wakes.
44
+
35
45
## Enabling Network Access
36
46
37
47
There are three ways to reach your server from another device: expose the desktop app's backend,
@@ -43,8 +53,9 @@ If you are already running the desktop app and want to make it reachable from ot
43
53
44
54
1. Open **Settings** → **Connections**.
45
55
2. Under **This environment**, toggle **Network access** on. This will restart the app and run the backend on all network interfaces.
46
-
3. The settings panel will show the default reachable endpoint, with a `+N` control when more endpoints are available. Expand it to inspect alternatives such as loopback, LAN, private-network, or HTTPS endpoints.
47
-
4. Use **Create Link** to generate a pairing link you can share with another device.
56
+
3. Turn on **Prevent automatic sleep** if this computer should stay reachable while unattended.
57
+
4. The settings panel will show the default reachable endpoint, with a `+N` control when more endpoints are available. Expand it to inspect alternatives such as loopback, LAN, private-network, or HTTPS endpoints.
58
+
5. Use **Create Link** to generate a pairing link you can share with another device.
48
59
49
60
The default endpoint controls the QR code and primary copy action for pairing links. You can change it from the expanded endpoint list. The preference is stored by endpoint type, so choosing the local LAN endpoint survives normal IP address changes when you move between networks.
0 commit comments