Guards

A tally of this session's permission checks: what was allowed, what you were asked about and what was denied.

Every failing check sends in an invader; every passing check shoots one down.

A numbered table of contents for the session, built as it happens from prompts, first edits, checks turning red or green, commits and questions; press a line to scroll the transcript to it

Conway's Game of Life; every tool call drops a glider.

Select a hash, path, name, timestamp or colour in the transcript with the mouse and the card says what it is, with no model call

A pixel map of the repository: every tracked file a block, lit blue where Claude has read and green where it has edited.

An LED ticker that scrolls session events across the card: turns, tool calls and failures.

A mosaic that gains one tile per tool call, coloured by tool, until the session is a picture.

Gives Claude a jot tool for writing down what its future self should know about this project, and reads the notes back next session

A small solar system whose planets speed up while tool calls are running.

When a push or install fails on the network, checks the provider's status page and says whether GitHub, npm, PyPI or crates.io reports an incident

Clawd, a pixel crab whose mood follows the session.

The conversation behind a line of code: for lines Claude is about to edit, or a path:line you ask about, the prompt you typed before they were written and the command that resumes that session

The session as a dungeon crawl: every turn is a room, tool calls are monsters, failures wound you and passing checks drop loot. Your hero carries over between sessions.

A race track for parallel subagents: each advances one stride per tool call, with a podium as they finish.

Falling code rain that speeds up while tool calls are running.

Replaces API keys, tokens, private keys and passwords in command output and file reads before Claude sees them

Which of the commands and edits Claude has made in this project would stop for permission or be refused right now, asked of the engine's own permission check without running anything

The pictures Claude looked at this session, image files it read and screenshots that came back from tools, drawn as Claude received them and opened full size with one command

A unique pixel emblem generated from each session's activity, kept in a gallery across sessions.

A pixel skyline: one building per turn, one floor per tool call.

A bar chart that sorts itself one swap per tool call, then reshuffles.

The session as music: a note per tool call, a chord when checks pass and a buzz on failure, with a piano roll. Playback currently works on macOS only.

Underlines file names that do not exist, as you type them in the prompt box, and paints the ones that do green