Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [FEATURE] Feature request: support persistent user tmux overrides from /config/.tmux.conf [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46777•Fetched 2026-04-12 13:33:18
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
pfurriepfurrie
Participants
pfurriepfurrie
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • 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

extent analysis

TL;DR

Modify the run.sh script to append user-defined tmux configurations to the copied ~/.tmux.conf file instead of overwriting it.

Guidance

  • Identify a persistent storage location for user-defined tmux configurations, such as a separate file in the /data/home directory.
  • Modify the run.sh script to check for the existence of this file and append its contents to the copied ~/.tmux.conf file.
  • Consider adding a new CLI command or flag to allow users to easily manage their custom tmux configurations.
  • Test the modified run.sh script to ensure that user-defined configurations are persisted across restarts.

Example

# Example modification to run.sh
if [ -f "/data/home/custom.tmux.conf" ]; then
  cat "/data/home/custom.tmux.conf" >> "/data/home/.tmux.conf"
fi

Notes

The proposed solution requires modifications to the run.sh script and may involve additional changes to the Claude Terminal configuration. The example provided is a minimal illustration of the concept and may need to be adapted to the specific requirements of the Claude Terminal environment.

Recommendation

Apply a workaround by modifying the run.sh script to support user-defined tmux configurations, as this will provide a immediate solution to the problem while a more permanent fix is developed.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#file not found#serialization error#model compatibility#GPU setup#container setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING