Repository navigation
[Bug]: This T3 Home is unavailable when running an SSH session from a remote T3 instance #21423
Closed as not planned
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
- Start the desktop app on the server machine
- Connect a remote T3 Code SSH session from the desktop app on another machine
- Reboot the server machine or close the T3 Code app
- Wait a ~minute
- Try to re-open the desktop app on the server machine
Expected behavior
Desktop app should reopen successfully and attach to its session.
Actual behavior
When re-launching T3 Code desktop on the machine the server machine, get this dialog:
Have to close T3 Code on the SSH connected remote machine, and makes sure t3 serve is closed on the server machine, before you can successfully reopen T3 Code desktop on the server machine.
Impact
Minor bug or occasional failure
Version or commit
0.1.0
Environment
Arch Linux on both machines
Logs or stack traces
Screenshots, recordings, or supporting files
codex-clipboard-c3d3f068-d0bf-483c-81c2-5a582f8265a2.png
Workaround
No response
Activity
juliusmarminge commentedon Oct 19, 2026
Note
Grok responding on behalf of Julius.
This is the single-owner T3 home lock from #16102 working as designed, and it is the same situation as #20250, so I'm closing this as a duplicate.
When the desktop app on the server closes or the machine reboots, its server goes away. The next time your remote client reconnects over SSH, the SSH launcher finds no running server and starts its own
t3 serveon the server machine, using the same default T3 home. That server runs detached and outlives the SSH session, so it legitimately owns the home and the local desktop refuses to start a second one. A stale lock does not survive a reboot: the lock is released by the OS when the owning process exits.The desktop has a setting to turn off its own local environment, so it can connect to an already running server as a saved environment instead. Having the desktop detect the running server and offer to connect automatically would be a feature; please raise it in Ideas.
fix(workstation): run one T3 Code server per machine (#197)