Skip to content
ModshelfSubmit

CC Tamagotchi

A virtual pet that eats Claude's edits and grows into one of eight adults

Just for funSide paneAbove the promptSpinner textLine under the promptPop-up notesSlash commandDraws only
CC Tamagotchi running in Claude Code

Recorded on Claude Code 2.1.287 in a sandbox. Claude's replies are scripted; everything the mod draws is real.

What it does

An egg appears the first time you start Claude Code with it, and /tama opens a pixel LCD in a pane beside the transcript. Once the egg is a minute old, it hatches at Claude's next tool call (or after three minutes on its own). From then on the pet lives off Claude's work: edits feed it, passing tests squash its bugs, failing tests leave new ones and commits throw a party. It also gets hungry, bored and sick, and calls you when it needs something. Over a few days it grows into one of eight adults, depending on how you cared for it and what Claude did most.

How to use it

  • /tama opens or closes the device. While the pane has the keyboard, its buttons have keys: F feed, S snack, P play, C clean, M medicine, L lights, D scold, I stats.
  • Every button is a command too: /tama feed, /tama snack, /tama play, /tama clean, /tama medicine, /tama lights, /tama scold, /tama stats.
  • /tama name <name> renames it, and /tama shell <color> picks the device's color (coral, mint, grape, sky, banana or ink).
  • /tama vacation on stops its clock while you're away. /tama mode gentle means it never leaves, however neglected.
  • /tama band sets how it shows above the prompt while Claude works (auto, big, on, line or off), and /tama spinner off takes its face away from the spinner.

Good to know

  • With the pane closed, the pet strolls above the prompt while Claude works. Its face rides beside the spinner, and the line under the prompt says when it needs you.
  • In the default classic mode, half a day of hard neglect and it leaves for good. /tama history lists the pets before it, and /tama new starts a new egg.
  • One pet per machine: every session shares it through the mod's own store. It looks at each tool call (and the text of shell commands) only to tell what kind of work it was: an edit, a test run, a commit. It makes no network calls and spends no tokens.