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
fix: use dedicated tmux socket to preserve TCC permissions across restarts (#42)
* fix: use dedicated tmux socket and kill server on quit to preserve TCC permissions
The tmux server survived Deckard restarts but retained stale TCC
permissions from the old Deckard process. macOS revokes TCC access
when the responsible app exits, causing "Operation not permitted"
errors in shells for protected directories like ~/Documents.
Fix: use a dedicated `-L deckard` socket (isolating from user tmux)
and kill the server on quit + launch so a fresh server with valid
TCC permissions is created each time.
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
* fix: keep tmux sessions alive across restarts, only isolate socket
The original fix killed the tmux server on quit, which lost all
terminal content — defeating the purpose of tmux persistence.
The TCC issue was likely a transient fluke (sleep/wake corruption),
not a systemic problem.
Keep the dedicated `-L deckard` socket for isolation from user tmux,
but restore session persistence: detach() on quit, orphan cleanup
on launch, and reconnect via -A on restore.
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
---------
Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
0 commit comments