zgbrenner gives Gary's drafts a one-click door into Word

Three export buttons under every AI answer move a draft into Word, email, or a template without a copy-paste mess.

draftingworkflow

zgbrenner added a small action row beneath each of Gary's responses: copy the draft, download it as a clean document, or pull it straight into Word with headings and bullets intact. The filename even carries the matter and task name, so what lands on your desktop isn't an untitled blob.

The one genuinely interesting call is what the export does not do: it never touches the AI's words on the way out. That sounds obvious until you realise legal drafts sometimes quote things that look like technical jargon - a licensing clause, a security term in a contract. zgbrenner wrote tests that lock this in, so that language survives the export unchanged, while the wrapper's own title block and the attorney-review reminder it stamps on every draft can never accidentally inject stray text of their own.

So what Worth a look for any team that wants a frictionless, low-surprise path from an AI answer to a Word document a lawyer can actually send.

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 zgbrenner/gary, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`b4345deb`	feat: add Copy Draft, Markdown, and Word export for AI outputs	Claude	2026-05-19	↗ GitHub
commit body Adds three export actions below every Gary assistant response so U.S. lawyers can move drafts into Word, email, or their own templates in one click: - "Copy Draft" - clipboard copy with HTML + Markdown payloads so paste into Word preserves headings and bullets; plain-English status text. - "Download Markdown" - `.md` file with safe filename like `contract-review-draft-2026-05-19.md`, wrapped with a short title block (matter, Saved Legal Task, date) and an attorney-review reminder. - "Download Word Draft" - `.docx` via the already-installed `docx` package; preserves headings, paragraphs, bullets, and simple GFM tables; ends with a short footer note. Helpers live in `frontend/src/lib/exportDraft.ts` and are reused by both the standalone assistant chat and the per-matter chat. Exports include only the assistant's prose - internal events, tool calls, IDs, and annotations are intentionally excluded. Adds focused tests in `exportDraft.test.ts` covering filename safety, header content, attorney-review reminder, no API-key/internal-ID leakage, and clipboard failure messaging. Updates the U.S. lawyer setup guide with a "Copying or Downloading Drafts" section, and extends the terminology map.
`347a4240`	fix: hide export row on very short replies; clarify no-scrub invariant	Claude	2026-05-19	↗ GitHub
commit body - AssistantMessage: only render Copy Draft / Download Markdown / Download Word Draft when the assistant's prose is at least 200 characters. Tiny conversational replies like "Done." or "I need more information." stay uncluttered. - exportDraft: document explicitly that the wrapper preserves AI content verbatim and never scrubs or redacts. The invariant we guard is the inverse - nothing the wrapper adds should introduce credential-shaped tokens. - exportDraft.test: add a positive test confirming that legitimate legal text discussing "API key" rotation or "Bearer token" authentication is preserved unchanged in the export.

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-575.md from inside the repo you want the changes in.

⬇ Download capture-thread-575.md