Repository navigation
Per-project terminal startup command (attach existing tmux sessions) #37308
rodchristiansen
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I run my coding agents in long-lived tmux sessions on an always-on Mac, one session per project folder. The same session is attached from several places at once: a desktop terminal, a couple of native Mac apps that embed a terminal, and Claude Code's own remote control. Because tmux owns the process, every client sees the same live TUI, and closing one never ends the agent.
T3 Code's iPhone and iPad apps are the best remote client I've found, but I can't reach those sessions from them, because every T3 terminal starts the login shell (#14611 confirms there's no setting for this today).
The request: let a project, or a single terminal, set a startup command and arguments that run in place of the default shell. For example
tmux new-session -A -s <name>. T3 would still own the PTY, so nothing changes for auth, scopes or the mobile client. The terminal just runs a different program.This is also the primitive step 2 of #25673 needs: a T3 terminal running
claude attach <id>for daemon-ownedclaude --bgsessions. And it covers zellij, screen,ssh host -t tmux attach, or any REPL someone wants pinned to a project.Possible shape:
t3.jsongetsterminal.commandandterminal.argsat project level, optionally as named profiles.If this fits the roadmap I'm happy to send the PR. Any pointers on where terminal spawn options should live in the contracts would help.
All reactions