Show HN: Clippy – 90s UI for local LLMs

Original Article ↗ Hacker News Discussion ↗

Nostalgia and 90s Aesthetic

  • Many commenters are delighted by the Windows 95/98-style UI and “terrible” bitmap-like font rendering, calling it “functional art” and saying it evokes strong childhood memories.
  • Some note that similar retro CSS/UX frameworks are maturing and that there’s a broader appetite for 90s/early‑web revival aesthetics.
  • Others argue nostalgia is misleading: people think they want old UIs but would quickly remember why they moved on.

Clippy’s Legacy and Brand

  • People debate why Microsoft hasn’t officially revived Clippy as a Copilot skin or avatar, seeing it as a huge missed branding and humor opportunity.
  • There’s disagreement over whether Clippy’s reputation (annoying, intrusive, useless) makes it toxic or perfect for self‑aware, ironic reuse.
  • Several recall that the original natural-language help behind Clippy was actually useful at times, especially for novices.

Trademark/IP Concerns

  • Multiple comments point out that “Clippy” (or “Clippit”) is still under Microsoft trademark activity, used in recent products and emojis.
  • Some think enforcement against a non‑commercial side project is unlikely; others note the narrow but active scope of the mark.

Implementation, Dependencies, and Electron

  • Strong reactions to the dependency bloat: the shipped bundle includes many seemingly unrelated libraries (templating engine, GitHub client, Math shim, etc.).
  • One maintainer explains this comes mainly via node‑llama‑cpp and that pruning dependencies in Electron apps is harder than it should be.
  • Critics argue that extra libraries increase attack surface, especially around templating and network‑capable dependencies.
  • There’s recurring desire for a non‑Electron, more native/lightweight version.

Local LLMs, Features, and UX

  • Users appreciate that it’s local‑only and easy to get running; some report specific errors on older Macs and confusion about moving the Clippy window.
  • Many request Ollama integration, API-key support for remote models, tool use, better personality tuning, and more assistants (Rover, the cat, dolphin, BonziBuddy, etc.).
  • Several want hotkeys, auto‑focus on the input, and clearer model performance expectations and model storage paths.

Future Assistant Concepts

  • A large subthread explores a “ClipGPT” that watches the screen (via screenshots or video) and proactively assists, raising concerns about privacy and user comfort.
  • Opinions diverge on whether non‑technical users would tolerate continuous screen capture; some think most would trade privacy for convenience.

Mixed Reception and Audience Fit

  • Many are effusively positive, calling it the first AI app they’re willing to install locally; others viscerally hate the Clippy persona and find it trauma‑inducing.
  • There’s tension between seeing this as a clever, joyful mashup versus “a basic app riding on stolen nostalgic IP” that crowds out more original work.