Every buddy is uniquely generated — same species, same stats, same personality every time. On Claude Code the seed is derived from your accountUuid in ~/.claude.json; on Pi and Oh My Pi a stable random UUID is generated once and persisted in ~/.pi/agent/buddy/identity.json or ~/.omp/agent/buddy/identity.json (deleting the file and letting it regenerate will change your buddy). 19 species, each with 3 idle animation frames + a blink.

 duck        goose       blob        cat         dragon      octopus
   __         (°>        .----.       /\_/\      /^\  /^\     .----.
 <(° )___      ||       ( °  ° )    ( °   °)   <  °  °  >   ( °  ° )
  (  ._>     _(__)_     (      )    (  ω  )    (   ~~   )   (______)
   `--'       ^^^^       `----'     (")_(")     `-vvvv-'    /\/\/\/\

 owl         penguin     turtle      snail       ghost       axolotl
  /\  /\      .---.       _,--._    °    .--.    .----.    }~(______)~{
 ((°)(°))    (°>°)       ( °  ° )    \  ( @ )   / °  ° \  }~(° .. °)~{
 (  ><  )   /(   )\      [______]     \_`--'    |      |    ( .--. )
  `----'     `---'       ``    ``    ~~~~~~~    ~`~``~`~     (_/  \_)

 capybara    cactus      robot       rabbit      mushroom    chonk
 n______n   n  ____  n    .[||].      (\__/)    .-o-OO-o-.  /\    /\
( °    ° )  | |°  °| |   [ °  ° ]    ( °  ° )  (__________)( °    ° )
(   oo   )  |_|    |_|   [ ==== ]   =(  ..  )=    |°  °|   (   ..   )
 `------'     |    |      `------'   (")__(")      |____|    `------'

Rarities

Colors use 24-bit true color matching Claude Code's dark theme exactly.

Stats

Every buddy has 5 core stats: DEBUGGING · PATIENCE · CHAOS · WISDOM · SNARK

High SNARK buddies are sarcastic. High WISDOM ones are insightful. High CHAOS ones are unpredictable. Each buddy has a peak stat and a dump stat.

Five integration points, zero binary dependencies. When Claude Code, Pi, or Oh My Pi updates, your buddy stays.

┌────────────── Claude Code (any version) ──────────────┐
│                                                        │
│   MCP Server    Skill       Status Line    Hooks       │
│  (buddy tools) (/buddy)    (animated art) (comments)   │
└───────────────────────┬────────────────────────────────┘
                        │ stable extension points
             ┌──────────┴──────────┐
             │    coding-buddy     │
             │                     │
             │  wyhash + mulberry32│
             │  18 species, 3 anim │
             │  rarity colors      │
             │  speech bubbles     │
             │  ~/.claude-buddy/   │
             └─────────────────────┘

• MCP Server — companion tools + system prompt that instructs Claude to write buddy comments
• Skill — routes /buddy, /buddy pet, /buddy stats, /buddy off, /buddy rename
• Status Line — animated ASCII art, right-aligned, with rarity color and speech bubble
• PostToolUse Hook — detects errors, test failures, large diffs in Bash output
• Stop Hook — extracts invisible <!-- buddy: ... --> comments from Claude's responses

Why MCP Instead of Binary Patching?

MCP is an industry-standard protocol. Skills are Markdown files. Hooks and status line are shell scripts. Nothing depends on Claude Code's binary internals.

Repository Layout

coding-buddy/
├── server/          # MCP server — tools, engine, art, reactions, state
├── skills/buddy/    # /buddy slash command
├── hooks/           # Thin Claude Code hook wrappers and phase-2 legacy bash hooks
├── server/hooks/    # Hook behavior implemented in TypeScript
├── statusline/      # Animated right-aligned buddy display
└── cli/             # install, show, hunt, verify, doctor, backup, uninstall

In Claude Code

CLI

You can run any command with npx -y @ramarivera/coding-buddy <command> from anywhere, or bun run <script> from a local clone.

_{💡 Want a global coding-buddy command? → cd coding-buddy && bun link}

🎯 Buddy Pick

Want a specific species, rarity, or stat distribution?

npx -y @ramarivera/coding-buddy pick

Interactive TUI with saved buddies, criteria search, vim keys, and two-pane preview. Uses the exact same wyhash + mulberry32 algorithm as Claude Code.

coding-buddy ships with built-in diagnostics for debugging across terminals and platforms.

bun run doctor

Complete diagnostic — environment, terminal info, state, settings, padding test, live status line output. Always run this first when filing a bug report.

bun run test-statusline

Temporarily replaces your status line with a multi-line diagnostic. Shows padding strategies side-by-side, color support, Unicode handling.

bun run test-statusline          # install test
# restart Claude Code, screenshot
bun run test-statusline restore  # restore buddy

bun run backup

Snapshot all coding-buddy state to a timestamped backup. Use before experiments.

bun run backup              # create snapshot
bun run backup list         # list snapshots
bun run backup restore      # restore latest
bun run backup restore <ts> # restore specific

Buddy not appearing in status line

1. Run bun run doctor — does the script work directly?
2. Restart Claude Code completely — instructions are loaded once at session start
3. Check ~/.claude/settings.json has the statusLine block
4. Make sure bun and jq are in $PATH

Buddy comments not showing

The buddy comment mechanism uses an MCP server instructions field that Claude only reads at session start. If you installed coding-buddy in an existing session, restart Claude Code.

jq '.mcpServers["claude-buddy"]' ~/.claude.json

Buddy art looks broken or misaligned

Known MVP issue on some terminal/platform combos — different terminals render Braille Pattern Blank (U+2800) at different widths.

To help us fix it:

1. Run bun run doctor and paste output in a new issue
2. Run bun run test-statusline and screenshot the result
3. Then bun run test-statusline restore

Recovery from a broken state

bun run backup restore      # restore latest backup
bun run uninstall           # full clean removal

Will I get the same buddy I had? Yes. coding-buddy uses the exact same algorithm as the original (wyhash + mulberry32, same salt, same identity resolution). For Claude Code, if your ~/.claude.json still has your accountUuid, you'll get the identical species, rarity, stats, and cosmetics. For Pi/OMP, keep ~/.pi/agent/buddy/identity.json or ~/.omp/agent/buddy/identity.json; the same stable UUID produces the same buddy. Resetting (deleting) that identity file generates a new random UUID and changes your buddy.