Terminal Output Capture And Replay

I got tired of sharing AI demos with terminal screenshots or screen recordings.Claude Code already stores full session transcripts locally as JSONL files. Those logs contain everything: prompts, tool calls, thinking blocks, and timestamps.I built a small CLI tool that converts those logs into an int

Unique: Preserves and replays ANSI-formatted terminal output as a first-class part of the session, not just code changes, enabling viewers to see build results, test output, and runtime behavior in context

vs others: More complete than code-only replay because it shows the full development workflow including compilation, testing, and execution, providing evidence that AI-assisted code actually works

via “terminal session state serialization and replay”

I've always had the urge to have my two macbooks communicate. Having one idle while working on the other felt like underutilization of resources. So I built Loopsy. Initially the goal was to do file transfer via local network, and then came running commands. I then tried running coding agents f

Unique: Implements session capture at the terminal I/O level with timestamp preservation, enabling deterministic replay with original timing rather than just storing command history

vs others: More detailed than shell history files because it captures output and timing, but less comprehensive than full system call tracing and requires more storage

via “output-capture-and-streaming”

** - AI pilot for PTY operations that enables agents to control interactive terminals with stateful sessions, SSH connections, and background process management

Unique: Implements asynchronous output capture with real-time streaming support to prevent buffer deadlocks in PTY sessions, using non-blocking I/O patterns — most subprocess wrappers use blocking reads which cause hangs with large outputs

vs others: Enables real-time output processing without blocking agent execution, whereas synchronous capture approaches require waiting for command completion before processing output

via “streaming output capture with real-time stdout/stderr access”

** - Run code in secure sandboxes hosted by [E2B](https://e2b.dev)

Unique: Provides real-time output streaming rather than buffering results until execution completes. Enables interactive monitoring and debugging workflows that would be impossible with batch-only output.

vs others: More responsive than polling-based output retrieval and more efficient than re-executing code to capture intermediate state. Comparable to local code execution but with network latency overhead.

via “terminal session recording and replay”

via “execution-result-capture-and-logging”