Contact
Contact tmux.app
Email hello@tmux.app. It is the only way to reach us, and every message is read by a person.
Quick answer
How do I contact tmux.app?
Send an email to hello@tmux.app. For a correction, include the page address and your tmux version (tmux -V). For a bug in tmux itself, use the tmux issue tracker instead.
What to email us about
Corrections
A command that fails, a key that does something else, a default that changed, a broken link. Tell us the page, what you ran, what happened, and your tmux version and OS. Email a correction.
Suggestions
A guide you could not find, a question our pages do not answer, a tool or workflow worth covering, or a part of the site that is hard to use. Email a suggestion.
Ads and privacy
Questions about the ads, analytics or cookies on this site, or a privacy request under GDPR or CCPA. The privacy policy explains what runs here. Email a privacy question.
Using our content
Questions about reusing our snippets or guides. Most of it is covered by the ISC license in our terms of service. Email us.
A correction we can act on quickly has these lines. Copy the template into your email:
Page: https://tmux.app/...
Section: heading near the problem
I ran: exact command or key
Expected: what the page says
Got: what happened, any error
Version: tmux -V output, your OSBugs in tmux itself
tmux.app is not part of the tmux project, so we cannot fix bugs in tmux or add features to it. If tmux crashes, draws the screen wrongly or behaves differently from its manual, report it on the tmux issue tracker on GitHub. Before you do, check the CHANGES file for your version (many "bugs" after an upgrade are documented changes) and our troubleshooting guide.
The tmux developers ask for the following in every report. Bug reports without logs may be closed without comment.
Collect your version and platform
shelluname -sp && tmux -V && echo $TERMRun
echo $TERMboth inside and outside tmux, and name your terminal (for example xterm, iTerm2, Ghostty or Windows Terminal). Inside tmux,$TERMshould betmux-256color,tmux,screen-256colororscreen.Reproduce without your config
Start a separate server that skips
~/.tmux.conf. If the problem goes away, it is caused by something in your config; remove lines until you find it.shelltmux -Ltest kill-server tmux -Ltest -f/dev/null newCapture logs
Add
-vvto write three log files to the current directory:tmux-server-PID.log,tmux-client-PID.logandtmux-out-PID.log.shelltmux -Ltest kill-server tmux -vv -Ltest -f/dev/null newIf you need your config to reproduce it, use
tmux kill-serverthentmux -vv new(this stops your running sessions). Attach the logs to the issue directly, zipped if they are large.Test the latest code
The developers ask that crashes and incorrect behavior be reproduced on tmux built from the latest code in Git. Distro packages are often several releases behind; see releases for how to check and upgrade.
For general tmux questions, the project runs the tmux-users mailing list. Security problems in tmux should be reported as described in the project's SECURITY.md, not in a public issue.
What to expect
- Corrections are checked on a real tmux build first. When we confirm one, we fix the page and update its date; see our corrections policy.
- We cannot promise a reply time. We read every message, but tmux.app is a small site. Corrections get priority over everything else.
- We cannot offer one-to-one support for your own setup, servers or configs. The troubleshooting guide covers the most common errors, and the tmux-users list is a good place for questions it does not answer.
- We do not sell placements. Requests for paid links, sponsored posts or guest posts will not get a reply.
We use your email address only to reply to you. We do not add it to a mailing list or share it with anyone.
Frequently asked questions
How do I report an error or outdated command?
tmux -V). If you know the fix, include it. We check every report on a real tmux build before changing the page.