foolish-bandit builds a plain-English decoder for legal text

A new page in the Gary fork turns dense legal language into a structured, four-part explanation anyone can follow.

summarizationchat-ui

Paste in a clause, a paragraph, or a whole provision, and the new "Explain This" page hands back an answer in a fixed shape: what it says, why it matters, what could go wrong, and a possible revision. You can optionally tell it the document type, your goal, and the tone you want, and it folds those into the request.

Unlike the fork's review and draft tools, this one works only on text you paste in - there's no document upload. That keeps it fast and low-friction for the everyday job of making sense of a single confusing passage rather than chewing through a full file. The three workflow shells are still bare-bones at this stage, with the polished interface arriving later.

So what Worth a look for anyone who spends their day translating legalese for clients or colleagues and wants a structured first pass.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from foolish-bandit/gary, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
b3287856 Add Explain This workflow shell Zack Brenner 2026-05-07 ↗ GitHub
35d1f06a Merge pull request #13 from foolish-bandit/codex/create-pr-#10-frontend-polish-and-bugfix-e39g9q Zack Brenner 2026-05-07 ↗ GitHub
Add 'Explain This' page, surface backend-unavailable messages, and UI/UX fixes

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-165.md from inside the repo you want the changes in.

⬇ Download capture-thread-165.md