The best way to control Claude Code, Codex and more from any computer or phone
Mirrored from https://github.com/Camo67/t3code.git
Synced Nov 22, 04:30 UTC
docs: scope managed-policy LAN note to old background services (#30900)
Co-authored-by: Victor Romo <vic@Victors-MacBook-Pro.local> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Victor Valentine Romo 🌴 committed
Nov 4, 2026 at 16:19 UTC
df70f505a3c3e3ad7ea0fde2ad2c01a6d57d2297
1 file changed
+4
-2
docs/user/managed-policy.md
+4
-2
@@ -224,8 +224,10 @@ desktop app, keep `desktop` in the list, or the app cannot start.
224
225
Without `remote`, the server listens only on a loopback address, creates no pairing links, and
226
signs out devices that paired earlier. It does not start with a host other than a loopback
227
-address or `localhost`. The [background service](./background-service.md) listens on private
228
-networks by default, so set `T3CODE_HOST=127.0.0.1` in its `service.env`. The desktop app starts
227
+address or `localhost`. A [background service](./background-service.md) installed before
228
+`T3CODE_LAN` existed keeps private-network access, so without `remote` it refuses to start.
229
+Run `t3 up --no-lan` when its `service.env` sets no `T3CODE_HOST`, or set
230
+`T3CODE_HOST=127.0.0.1` in `service.env`, then run `t3 service restart`. The desktop app starts
231
with network access and Tailscale Serve off, whatever the user chose. That also turns off
232
T3 Connect. To keep other remote access but turn off T3 Connect alone, set `"connect": false`.
233