Iris

Iris is a command-line tool that records terminal debugging sessions into structured JSON artifacts called .trace files — every command, every output, every exit code, every timestamp stored as separate searchable fields.

## The Problem

You debug for 3 hours, fix it, and the next day someone asks what you did. Terminal history shows commands but no output. Screenshots capture one moment, not the sequence. Raw logs are full of unreadable escape codes. asciinema records video you can't search. There is no existing tool built specifically for sharing a complete debugging journey.

## Who it helps

- Junior developers who can't explain what happened during debugging

- Senior developers drowning in blurry screenshots over Slack

- Open source maintainers who can't reproduce bugs from incomplete reports

## What makes it different

- Structured JSON output — grep it, query it, parse it programmatically

- Auto-redacts passwords, API keys, and tokens before saving

- Cross-platform — Linux and macOS use native pty, Windows uses pywinpty

- Zero dependencies on Linux/macOS — pure Python stdlib

- The receiver needs nothing installed to read a .trace file

## Usage

iris record # start recording

iris search "error" session.trace # search a session

iris replay session.trace # replay what happened

iris summary session.trace # stats and error count

iris export session.trace --output report.txt # shareable text

## FOSS Compliance

MIT licensed. No closed-source dependencies. No external APIs. No cloud. Everything runs and stays local.