pkg.sopackage field notes

brew / Rang 134

tmux mit Homebrew installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für tmux in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install tmux

provider-native install command

Überblick

Paketzusammenfassung

Terminal multiplexer

Befehle und Aliase

  • tmux

Verlauf

Projektgeschichte und Nutzung

tmux is a terminal multiplexer: it lets users create, access, control, detach, and reattach multiple terminal sessions from one screen. It is one of the defining tools of modern command-line workflows, especially for developers, sysadmins, and package-manager users who keep reproducible terminal environments.

Projektgeschichte

Official OpenBSD documentation records tmux as started in 2007 by Nicholas Marriott, imported into OpenBSD on June 1, 2009, and first released with OpenBSD 4.6. The upstream CHANGES file records an initial CVS import on July 9, 2007, when detaching, reattaching, creating sessions, and listing sessions already worked well enough for shells, with status bar and customization still missing.

tmux's development model is unusual among popular developer tools: the tmux wiki states that OpenBSD CVS is the primary source repository and that GitHub carries the portable version, with a script applying OpenBSD commits to GitHub every few hours. This keeps tmux rooted in OpenBSD base-system practice while making it available as a portable package for other Unix-like systems.

Adoptionsgeschichte

tmux grew from an OpenBSD base utility into a cross-platform terminal standard. The official README says current releases run on OpenBSD, FreeBSD, NetBSD, Linux, macOS, and Solaris, and the batch input records package names across apk, Homebrew, Debian, dnf, MacPorts, Nix, pacman, Ubuntu, and zypper.

By 2026, the GitHub repository and wiki showed a large public footprint, including tens of thousands of stars, a public issue tracker, a wiki, releases, and a tmux-users mailing list. The project remained volunteer-developed but widely relied on, with releases documented through GitHub release pages and the CHANGES file.

Wie es verwendet wird

tmux is used to keep long-running terminal work alive across disconnects, split a terminal into windows and panes, switch between programs, script terminal layouts, and share or inspect sessions. Its configuration files, commonly /etc/tmux.conf and ~/.tmux.conf, are central to dotfiles culture.

In the package-nerd niche, tmux is also a platform for other packages. Several packages in this same batch, including tmux-mem-cpu-load, tmux-sessionizer, and tmux-xpanes, exist because tmux exposes stable session, pane, status-line, and command interfaces that small tools can compose with.

Warum Paket-Nerds sich dafür interessieren

tmux matters to package users because it is both an application and a substrate. It is packaged nearly everywhere, has a small and documented dependency stack, and creates an ecosystem where status monitors, pane launchers, session switchers, and dotfiles plugins can be distributed independently.

Zeitleiste

  • 2007: Nicholas Marriott started tmux, according to OpenBSD's innovations page.
  • 2007-07-09: Upstream CHANGES records the initial CVS import with sessions, detach, reattach, and shell use already working.
  • 2009-06-01: tmux was imported into OpenBSD.
  • 2009: tmux first shipped with OpenBSD 4.6.
  • 2026: GitHub releases page listed tmux 3.7b as the latest bug-fix release.

Related projects

  • OpenBSD is the primary upstream home for tmux development.
  • GNU screen is the older terminal-multiplexer tradition that tmux belongs beside, though tmux's official docs emphasize tmux's own client-server, sessions, windows, and panes model.
  • tmux-mem-cpu-load, tmux-sessionizer, and tmux-xpanes are package-level examples of the tmux ecosystem.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für tmux wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
/etc/tmux.conf~/.tmux.conf

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
tmuxExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-08-03
Manager-Version3.7b
Manager aktualisiert2026-07-01
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:tmux
Version3.7b
PaketmanagerHomebrew
Homepagehttps://tmux.github.io/
Repositoryhttps://github.com/tmux/tmux
Zuletzt aktualisiert2026-07-01T22:33:19Z
Pulseupdated
Bottlenicht erfasst
Dienstkeiner deklariert

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • curated configuration and credential file locations
  • curated package history
  • pkgdb category and tag curation