"I'll remember!" Famous last words.
You spend two hours chasing a bug, hardening a server or deploying a service. The veteran in you knows you should document the steps as you go. The optimist in you says "I'll remember!" and, as usual, the optimist wins.
Two hours and a few hundred commands later (including editing dozens of files by hand), it works. Then the meeting reminder pops up and before you know it - the day ends. By tomorrow the details are fuzzy. In a week, they're gone.
Enter trecs, a terminal recorder that does the remembering:
• Transparent: run trecs record, then work exactly as you normally would
• Every command and its full output, with ANSI colours, ncurses/TUI apps and sixel images intact
• Each command is marked, so you jump between them instead of scrubbing through two hours of text
• Since it's all text, you can copy full screens or individual lines straight off the player
• Search the recording for that one elusive build error, or the config line you added
• A Markdown write-up of every command and output, generated automatically
• Edit afterwards: delete commands, add annotations and images, merge recordings
• Record audio narration live, or add it later
Terminal recorders are not a new concept, with the first one probably being the script util, back in the late 1970s. With trecs, I aim to get the most out of the idea.
The trecs recorder and TUI editor are both free and open source (AGPLv3).
Want to share a recording or view it from anywhere? Upload it to https://trecs.run
trecs is written in Golang and both binaries (the recorder and TUI editor) are statically linked, so deployment is super easy and quick. See releases for deb, RPM, ZST packages and pre-built binaries.
Feedback, feature requests and contributions are most welcome:)
Top comments (0)