⚖MikeWatch Forks of the Mike legal-AI codebase, distilled for legal-tech readers
Home · foolish-bandit/gary · this thread

foolish-bandit strips the developer-speak out of the settings page

The account screen now talks to lawyers, not engineers.

chat-uipersonas

foolish-bandit went through the settings and model-selection screens and rewrote the labels for people who don't think in code. "Models & API Keys" became "AI configuration." The section where you connect your own AI account no longer talks about pasting keys into a config file "for the app to work" - it explains, in plain terms, that you're linking an outside AI service and what happens once you do. Even the greyed-out options now tell you exactly where to go to switch a key on.

Nothing under the hood changed: same connections, same behaviour. This is purely about whether a non-technical user can sit down with the product and not feel locked out by jargon.

So what If you're putting Mike in front of legal-ops staff or end clients rather than your own engineers, this is the kind of polish that decides whether they get past the first screen.

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
3c80d724 Merge pull request #10 from foolish-bandit/claude/rename-copy-cleanup Zack Brenner 2026-05-07 ↗ GitHub 
De-jargon user-facing model/API-key copy
2ea104bd De-jargon user-facing model/API-key copy Claude 2026-05-07 ↗ GitHub
commit body 
Frontend-only copy cleanup. No identifiers, file names, MIME types,
localStorage keys, env vars, or backend contracts were renamed -
those carry behavior and were intentionally left alone.

User-facing changes:
- Account settings tab "Models & API Keys" → "AI configuration".
- /account/models page:
  - "Model Preferences" → "Default assistant"
  - "Tabular review model" → "Assistant for tabular reviews"
  - "API Keys" → "AI service keys"
  - Body copy rewritten to plain English ("GaryOSS connects to an
    outside AI service to answer questions...").
  - "Anthropic (Claude) API Key" → "Anthropic (Claude) key"
  - "Google (Gemini) API Key" → "Google (Gemini) key"
  - Tooltip "Add a {vendor} API key to use this model" →
    "Add a {vendor} key in AI configuration to use this assistant"
  - Placeholder "Select a model" → "Select an assistant"
- ApiKeyMissingModal:
  - Title "API key required" → "GaryOSS isn't configured yet"
  - Body softened to "GaryOSS isn't connected to {service} yet.
    Open AI configuration to add a key."
  - CTA "Go to account settings" → "Open AI configuration"
- ModelToggle:
  - title "API key missing for selected model" → "No key set for
    this assistant"
  - title "Choose model" → "Choose assistant"
  - aria-label "API key missing" → "No key set"
  - Fallback label "Model" → "Assistant"

GaryOSS branding is already consistent in README, layouts, and
schema header. No backend files touched. 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-163.md from inside the repo you want the changes in.

⬇ Download capture-thread-163.md