[FEATURE] Feature request: support persistent user tmux overrides from /config/.tmux.conf

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Claude Terminal ships a solid base tmux config at /opt/scripts/tmux.conf, which run.sh copies to ~/.tmux.conf (/data/home/.tmux.conf) on every startup. This is the right design — it ensures a known-good baseline after every restart.

However, users who want to adjust tmux behavior (scroll keybindings, mouse mode, copy behavior, status bar tweaks, etc.) have no persistent path to do so today:

• /opt/scripts/tmux.conf is ephemeral — reset from the Docker image on every restart
• /data/home/.tmux.conf is overwritten by run.sh on every restart, so manual edits there don't survive
• Claude Code hooks cannot be used for terminal setup (a SessionStart hook causes CC to exit immediately on startup — see the known issue)

The result: any tmux customization must be re-applied manually after every CT restart.

Proposed Solution

Claude Terminal ships a solid base tmux config at /opt/scripts/tmux.conf, which run.sh copies to ~/.tmux.conf (/data/home/.tmux.conf) on every startup. This is the right design — it ensures a known-good baseline after every restart.

However, users who want to adjust tmux behavior (scroll keybindings, mouse mode, copy behavior, status bar tweaks, etc.) have no persistent path to do so today:

• /opt/scripts/tmux.conf is ephemeral — reset from the Docker image on every restart
• /data/home/.tmux.conf is overwritten by run.sh on every restart, so manual edits there don't survive
• Claude Code hooks cannot be used for terminal setup (a SessionStart hook causes CC to exit immediately on startup — see the known issue)

The result: any tmux customization must be re-applied manually after every CT restart.

Alternative Solutions

Had Claude Code try other ideas that it thought would work, but none of them worked. Its final analaysis was that posting a feature request to you was the best course of action.

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_