foolish-bandit gives Mike a guided contract-review on-ramp

A frontend-only wrapper turns the assistant into a structured contract reviewer without touching the backend.

contract-reviewchat-ui

@foolish-bandit added a three-step shell that walks a lawyer through picking or uploading a contract, shows an eleven-point checklist of what the assistant will look for - parties, dates, governing law, payment terms, termination, indemnity, confidentiality, assignment, dispute resolution, unusual or risky clauses, and missing clauses - and then hands the work off to the existing chat. A canned review prompt is bundled in the page, citations are promised on every finding, and an AI-is-not-legal-advice disclaimer sits on the screen before the user kicks off.

Nothing new gets persisted: the review is just a chat thread, scoped to a single document, with no separate failure state and no sidebar entry. The home card's Review Contract button now lands here; the older cross-document tabular review is still in the sidebar untouched. It's framing, not new plumbing.

So what Worth a look for legal-product teams weighing how much value you can add by wrapping an existing chat assistant in a task-shaped UI instead of building a new feature underneath.

View this fork on GitHub →

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

Commits in this thread

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

SHA Subject Author Date

16c7bffd Add /review contract review shell Claude 2026-05-07 ↗ GitHub

SHA	Subject	Author	Date
`16c7bffd`	Add /review contract review shell	Claude	2026-05-07	↗ GitHub
commit body Builds a frontend-only Contract Review flow that reuses the existing upload, document picker, and assistant chat plumbing - no new backend routes. - New route at /review with a 3-step lawyer-friendly UI: 1. Choose contract (existing FileDirectory single-select + upload via uploadStandaloneDocument) 2. Confirm review (selected doc, what Gary will look for, citation expectation, "answers are not legal advice") 3. Review key terms (handed off to the assistant chat) - Start Review builds a MikeMessage with a fixed review prompt and the chosen document, then reuses useAssistantChat.handleNewChat + router.push("/assistant/chat/{id}"), the same path used by the Gary-mode home InitialView. The new chat page auto-sends the prefilled message and streams the cited response. - Updates the Gary-mode "Review Contract" card to point at /review instead of /tabular-reviews. /tabular-reviews is unchanged and still reachable from the sidebar. No backend changes, no API contract changes, no auth/billing/teams, no new providers. License unchanged. https://claude.ai/code/session_019pRkhcGDRKQWHjzAnV5yCL

commit body

Builds a frontend-only Contract Review flow that reuses the existing
upload, document picker, and assistant chat plumbing - no new backend
routes.

- New route at /review with a 3-step lawyer-friendly UI:
    1. Choose contract (existing FileDirectory single-select +
       upload via uploadStandaloneDocument)
    2. Confirm review (selected doc, what Gary will look for,
       citation expectation, "answers are not legal advice")
    3. Review key terms (handed off to the assistant chat)
- Start Review builds a MikeMessage with a fixed review prompt and
  the chosen document, then reuses useAssistantChat.handleNewChat
  + router.push("/assistant/chat/{id}"), the same path used by
  the Gary-mode home InitialView. The new chat page auto-sends
  the prefilled message and streams the cited response.
- Updates the Gary-mode "Review Contract" card to point at /review
  instead of /tabular-reviews. /tabular-reviews is unchanged and
  still reachable from the sidebar.

No backend changes, no API contract changes, no auth/billing/teams,
no new providers. License unchanged.

https://claude.ai/code/session_019pRkhcGDRKQWHjzAnV5yCL

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

⬇ Download capture-thread-272.md