The log told the truth, but no one was looking.

Tmux keeps your work alive long after a terminal dies. It splits, detaches, and resumes like nothing happened. But when something goes wrong, and you need to know what happened inside those panes, you realize a hard truth: tmux has no native audit log. No history of commands, no replay of actions, no trace of what you or someone else did in that session.

This gap matters. In security reviews, incident reports, or debugging at 3 a.m., knowing exactly what commands ran is everything. Without audit logs for tmux, you rely on memory, screenshots, or scattered shell history—none of which give you a full, trustworthy record.

Audit logging for tmux means capturing every keystroke, every command, every output, with a time signature you can trust. It means you can play back activity exactly as it happened. It closes the blind spot that exists between opening a terminal and logging into a server. For teams, it means accountability without slowing anyone down. For compliance, it means proof where none existed.

The technical goal is simple: wrap tmux sessions in a system that captures streams of activity in real time, stores them securely, and makes them searchable. That requires interception at the terminal I/O level, session indexing, and reliable persistence to a log backend. Engineers know this isn’t just about writing to a file—it’s about avoiding data loss, ensuring integrity, and keeping log access controlled.

You can build it yourself, but it’s slow and brittle. Or you can run it now.

Hoop.dev gives you tmux audit logs without changing your workflow. You launch tmux like always, but every session is recorded, indexed, and ready to replay. Search by command, time, or session. Audit logs for tmux, live in minutes.

See it for yourself. Try hoop.dev and watch tmux sessions become searchable truth.