Skip to content

Commit 8df4ab6

Browse files
committed
docs: when systemd stops agent servers, and tmux attribution
The systemd cleanup runs when an agent or terminal starts after a restart, not at the restart itself. tmux can keep an earlier agent's thread id and attribute later servers to that thread.
1 parent 34bb281 commit 8df4ab6

1 file changed

Lines changed: 6 additions & 1 deletion

File tree

‎docs/user/thread-sidebar.md‎

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -230,7 +230,8 @@ finishes; the call's own result shows its status.
230230
On web and desktop, the thread details card lists the web servers that the
231231
thread's terminals or its Claude agent started, with their ports. A server the
232232
agent started stays listed after the agent finishes or the thread settles. On
233-
Linux with systemd, T3 Code stops the servers agents left when it restarts.
233+
Linux with systemd user scopes, T3 Code stops servers left by agents when it
234+
starts an agent or terminal after a restart.
234235
Select a server to open it in the browser panel. **Stop** ends the server's job
235236
and keeps the agent, the terminal, and T3 Code running. Stop needs terminal
236237
access to the environment. On Windows, the card lists only servers started in a
@@ -240,6 +241,10 @@ A server the agent starts through a tool that passes on only some environment
240241
variables, such as Turborepo in its default strict mode, is not listed. To list
241242
it, add `T3CODE_THREAD_ID` to `globalPassThroughEnv` in `turbo.json`.
242243

244+
Long-lived launchers such as tmux can keep the thread id they inherited from
245+
an earlier agent. Servers they start later can appear under that earlier
246+
thread, so check the port before stopping one.
247+
243248
## Snooze until later
244249

245250
Choose **Snooze → Custom…** from a thread's menu to pick a date and time in your

0 commit comments

Comments
 (0)