All pages
Docs · AI features
Terminal history
Availability: macOS.
TRMNLY can keep everything your panes print, as plain text you can read, search and grep later. That includes output that scrolled away and panes you closed days ago. Each file says which project, tab and pane it came from.
Settings → AI Agent → Terminal history.
Modes
- Off: nothing is recorded. This is the default. Files already kept stay.
- On this Mac: each pane's output is written to
~/Library/Application Support/TRMNLY/terminal-history/<yyyy-mm-dd>/<pane-id>.log, one file per pane per day. A file that passes 16 MB continues in<pane-id>-2.log. Show in Finder opens the folder. - On this Mac and on trmnly.dev: the same, plus each file is uploaded to your trmnly.dev account once its pane has been quiet for ten minutes. It is compressed and stored encrypted next to your conversation archive, and counts toward the same 2 GB. Files show up at trmnly.dev/app/conversations under the source "Terminal", with the project and the tab/pane as the title. This mode needs the Mac to be signed in to trmnly.dev (Settings → AI Agent → Remote control).
Delete history on this Mac after sets how long local files are kept: 30 days, 90 days (the default), 1 year, or never. Deleting local files doesn't delete their cloud copies. Those are deleted at trmnly.dev/app/conversations.
What a file looks like
# TRMNLY terminal history
# Started: 2026-10-22 14:03:22 -07:00
# Mac: Will's MacBook Pro
# Project: TRMNLY
# Project folder: /Users/me/Workspace/TRMNLY
# Project id: 6F1C…
# Tab: zig build
# Tab id: 3A90…
# Pane: zsh
# Pane id: 9B2E…
# Directory: /Users/me/Workspace/TRMNLY
$ zig build test
…
── 2026-10-22 14:20:05 -07:00 · project TRMNLY · tab "zsh" · pane "zsh" · /Users/me/Workspace/TRMNLY/site ──
$ npm test
…
── 2026-10-22 15:02:40 -07:00 · pane closed ──
A dated ── line is written when:
- the pane's directory, tab or project changes;
- output resumes after five minutes of silence;
- the pane picks up again after a restart;
- the pane closes;
- history is turned off.
What is recorded
- The text that was printed, without colours, cursor movement or window titles. A progress bar that redraws itself on one line is kept in its final state.
- Full-screen programs (vim, less, htop, anything using the alternate screen)
are not recorded. The file has a
[full-screen program]line where one ran. - Programs that redraw in place on the normal screen (Claude Code, npm and cargo spinners, anything built on Ink) keep only their last frame. The last 200 lines stay editable and are written once they scroll out or the pane has been quiet for 10 seconds, so a cursor moving back up to rewrite a line rewrites it in the file too. A redraw that reaches further back than that is written again below.
- After a restart, the screen TRMNLY repaints isn't written a second time.
- tmux and screen run on the alternate screen, so a pane running them
records only the
[full-screen program]line. Programs that place text at absolute screen positions on the normal screen, which is rare, come out jumbled. - Wide characters (CJK, emoji) take their two columns, so redraws over them line up.
- A line longer than 16,384 characters wraps onto the next line.
- What you type is in the file only as the terminal echoed it. Password prompts that hide your typing aren't recorded. Anything a command printed is recorded, secrets included. Treat the folder and the cloud copy accordingly.
- If TRMNLY crashes, the last few seconds of output can be missing, as can up to 200 lines a busy pane hadn't settled yet. Quitting normally writes everything.
- If you delete the folder or a file while TRMNLY is running, the next output starts a new file with a fresh header.
- Files are filed under the day in your current time zone, and follow you if you travel.
- In the cloud mode, conversations upload before terminal history, so busy panes can't fill the 2 GB ahead of them.
terminal_history_searchreads at most the newest 512 MB per call, and says so when it stops early.- If a pane prints more than 8 MB in three seconds, the rest of that burst is skipped, and the file says how many bytes were left out.
Asking the agent
The Agent sidebar has two tools for this history. Claude Code and Codex running in a pane get them over MCP too.
terminal_history_search: find a line across every kept file, as a case-insensitive substring or a regular expression. Filter byproject,pane_idordays. Each match names its file, line number, project, tab and pane.terminal_history_read: read a file, or a window of one, bypathor bypane_id. With neither, it lists recent files.
So you can ask things like "what did the build print yesterday in the TRMNLY project?" or "find the error from the migration I ran this morning".
This is separate from the 256 KB tail each pane keeps so it can be repainted after a restart (see Claude Code sessions). That tail is saved once a pane's output settles, or every two minutes while it keeps going (a status line or full-screen program never goes quiet), off the main thread; quitting saves every pane. It is still deleted when a pane closes. The history file is kept.