Ep 12: Advanced Troubleshooting Q&A

⏱ Est. reading time: 3 min Updated on 5/7/2026

Practical solutions for co-existing terminals, performance tuning, handling remote disconnects, and resolving configuration conflicts.

Q6: I have Ghostty, iTerm2, and Warp all installed. How do I manage them without conflicts?

Multiple terminals can coexist perfectly. They share shell configurations (like ~/.zshrc) but maintain independent UI settings. Choose one as your primary and open others only as needed.

Q7: The terminal freezes when an Agent outputs too much data. What should I do?

  • Ghostty / cmux: Rarely freezes due to GPU rendering. For extreme loads, increase the scrollback-limit.
  • iTerm2: CPU rendering is prone to lag. Limit the scrollback buffer lines or disable infinite scroll.
  • Warp: High UI overhead. Try disabling AI auto-completions in settings.

Q8: My tmux session is gone! Can I recover it?

  • System Restart: The tmux server was killed; sessions cannot be recovered unless you use the tmux-resurrect plugin for automatic saving.
  • Accidentally Killed Session: Cannot be recovered; you must recreate it.
  • SSH Disconnect: The session is still running in the background. Simply reconnect and run tmux attach.

Q9: How do I resolve shortcut conflicts between tmux and Claude Code?

The best solution is to change your tmux prefix key from the default Ctrl+b to Ctrl+a or Ctrl+Space. This avoids conflicts with most CLI tools.

Q10: My company server only allows SSH and has no GUI. What's the best Agent terminal setup?

The Ultimate Setup: Ghostty (Local) + SSH + tmux (Remote). Ghostty provides the fastest local rendering, while tmux ensures that even if your connection drops, the remote Agent continues its task.

Appendix: Core Configuration References

Ghostty (~/.config/ghostty/config):

theme = catppuccin-mocha
scrollback-limit = 100000

tmux (~/.tmux.conf):

set -g mouse on
set -g history-limit 100000
set -g prefix C-a
unbind C-b
bind C-a send-prefix