James Washington
writing about archive utils free game ideas replays
Technique

Manually scan session replays before publishing

Auto-redaction of AI session recordings misses some login cookies, so check by hand.

Upgrading the AI's workbench

how it works

claude-replay's redactor missed site session cookies; grep for cookie names/tokens before publishing scraper sessions (a leaked replay was later removed).

Technique: A pattern or hard-won lesson, written down so it isn't learned twice.

The code for this one lives in a private repo. This page explains the idea so you can build your own.

publishingredactionsecuritytechnique

related

  • /claude-replay: session to interactive replay post Slash command Turns an AI coding session into an interactive replay published on the blog.
  • Claude Code session replays section Thing A page for interactive replays of AI coding sessions.
  • PostToolUse file soft-claim hook for agent collision detection Agent hook Every time an AI session edits a file, it quietly tells the dashboard, so two sessions editing the same file get flagged.
  • Mission Control presence/telemetry hooks Agent hook Every AI session automatically shows up live on the operations dashboard: when it starts, works, edits files and stops.
  • Claude Code session explorer (FTS5) Command-line tool Search every past AI conversation across all projects and jump back into one.
← everything I've built
© 2026 James Washington
github twitter rss