VS Code Pets

Original Article ↗ Hacker News Discussion ↗

Overall reaction & nostalgia

  • Many find VS Code Pets charming, cute, and morale-boosting, with some saying they use it daily or that it got non-technical partners interested in what they’re doing.
  • Strong nostalgia for earlier “desktop pets” and agents: Neko, eSheep, BonziBuddy, Microsoft Bob/Agents (Clippy, Peedy, Merlin, etc.), Tiny Elvis, and similar gimmicks in music or coding tools.
  • Some see it as part of a long-running tradition of playful UI elements, not a novel concept.

Requested features & behavior

  • Desire for pets inside the editor itself rather than confined to side panels, including walking across the whole screen, sitting on window bars, or living in the status bar.
  • Multiple ideas for code-aware behavior:
    • Reacting to code under the cursor, loops, function signatures, infinite loops, or line length violations.
    • Reflecting linter status, compile errors, or general workspace health.
    • Tying pet visibility to variable scope or symbol presence.
  • Several “Tamagotchi” concepts: pets that get sick or die if errors pile up, work is not completed, or breaks aren’t taken, and pets that “eat” obsolete code or comments.
  • Requests for size controls on high‑DPI screens; this already exists in settings.

Productivity vs. distraction

  • Some insist it’s purely a distraction and question any productivity benefits.
  • Others argue it provides:
    • Short mental breaks.
    • Stress relief and making boring tasks more tolerable.
    • A “rubber duck debugging” focus point while thinking.
  • There’s disagreement whether unsolicited, animated distractions are helpful or harmful.

Alternatives & related tools

  • Mentions of similar features in Google Colab (corgi mode), internal Google IDEs, JetBrains (Nyan progress bar, power mode), and Neovim pets.
  • References to other desktop companions (Desktop Mate, Desktop Goose, FL Studio’s dancing character).

Pranks, security, and culture

  • Multiple anecdotes about humorous browser/desktop extensions and fake error/update screens used to “teach” people to lock their computers.
  • Strong disagreement over whether such pranks are acceptable security culture or grounds for termination, highlighting differing workplace norms and trust expectations.