Update

2026-10-12 03:10:25 +02:00
parent 9b57f936b8
commit f9c48c6b93
3 changed files with 393 additions and 44 deletions
@@ -205,7 +205,7 @@ A chunk hit from `search` returns **the actual chunk text**, not just FTS's high

 `export_terminal_log` is only ever offered inside a live tmux session (see the environment-gating section above — this is the tool `TOOL_ENV_GATES` exists for). When it's available, it runs `tmux capture-pane -p -S -` — the **entire** pane scrollback, not just what's currently visible — writes it verbatim to `~/.tai/termlogs/<profile>/<pane>-<timestamp>.log`, saves it as a `termlog`-kind vault record for provenance and full-text paging, and immediately chunks and indexes it exactly like everything else above. From that point on, "what was that error three hundred lines back" is a `search` call, not a scrollback hunt — the parent record stays for full context, the chunks stay for precision, and the whole thing cost one tmux subprocess call and zero network requests.

-Its quieter cousin, `get_current_terminal_content`, grabs just the visible pane (configurable line count) for a quick glance without writing or indexing anything — the difference between a peek and a capture is deliberate.
+Its quieter cousin, `get_current_terminal_content`, grabs just the visible pane (configurable line count) for a quick glance without writing or indexing anything, the difference between a peek and a capture is deliberate. It also appends recent shell history, takes a `target` pane to peek at other terminals, and has two siblings: `list_terminals` for counts and ids of every open terminal, `tail_terminals` for the last 3 lines of each at once.

 ---