foolish-bandit scrubs the engineer-speak out of settings

The fork's AI configuration page now talks like a product, not a developer console.

chat-uibranding

The team went through the screen where users plug in their AI provider keys and rewrote the labels for a non-technical reader. "Models & API Keys" becomes "AI configuration." "Model Preferences" becomes "Default assistant." Even the empty-state warning shifts from a curt "API key required" to a friendlier "GaryOSS isn't connected yet - open AI configuration to add a key."

Notably, the change is skin-deep on purpose. Nothing behind the labels was renamed, so existing integrations and stored settings keep working. It's a copy pass, not a refactor - the kind of small move that quietly signals who the fork thinks its users are. The word "model" gets replaced by "assistant" throughout, which lands better with lawyers who don't think of their tools as machine-learning artifacts.

So what If you're shipping legal AI to non-engineers, this is a cheap, low-risk pattern worth stealing: rewrite the settings screen before users ever see the word "API."

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