Showing the changes to docs/user (1 of 12 files). Show all
Unified · Split
| @@ -1,7 +1,14 @@ | ||
| 1 | 1 | # Running T3 Code in the Background |
| 2 | 2 | |
| 3 | −On a Linux host, T3 Code can run as a background service for your user. It starts when the machine | |
| 4 | −boots and keeps running after you log out. | |
| 3 | +On macOS or Linux, T3 Code can run as a background service for your user. The simplest setup is: | |
| 4 | + | |
| 5 | +```sh | |
| 6 | +npx t3 connect | |
| 7 | +``` | |
| 8 | + | |
| 9 | +After T3 Connect links the machine, accept the default background setup. T3 Code starts immediately | |
| 10 | +and returns automatically after a reboot. On macOS, the per-user LaunchAgent starts after you sign | |
| 11 | +in. On Linux, the systemd user service starts at boot and keeps running after you log out. | |
| 5 | 12 | |
| 6 | 13 | ## Manage the Service |
| 7 | 14 | |
| @@ -33,10 +40,10 @@ Updating restarts T3 Code briefly. Let active agent work and terminal commands f · 25 unmodified lines | ||
| 33 | 40 | |
| 34 | 41 | ## Using It with T3 Connect |
| 35 | 42 | |
| 36 | −T3 Connect may offer to install the service during setup so the host stays reachable after you log | |
| 37 | −out. This is only an onboarding shortcut: the service and T3 Connect are managed separately. | |
| 43 | +T3 Connect offers to install the service during setup so the host starts automatically and stays | |
| 44 | +reachable in the background. The service and T3 Connect are still managed separately. | |
| 38 | 45 | |
| 39 | 46 | Signing out of T3 Connect does not remove the service. Use `t3 service uninstall` when you no longer |
| 40 | 47 | want T3 Code to start in the background. |
| 41 | 48 | |
| 42 | −The background service currently requires Linux with systemd. | |
| 49 | +The background service requires macOS with launchd or Linux with systemd. | |