claude-pet 2.0.0

package/.claude/commands/feed.md

@@ -0,0 +1,28 @@
+Feed your Claude Pet!
+
+Appends a feed event to the pet's event file so your desktop pet reacts with a happy eating animation. Shows current pet status after feeding.
+
+```bash
+mkdir -p ~/.claude-pet && echo '{"type":"feed","timestamp":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' >> ~/.claude-pet/events.jsonl
+
+node -e "
+const fs=require('fs'),os=require('os'),p=require('path'),h=os.homedir();
+const pl=os.platform();
+const d=pl==='win32'?p.join(process.env.APPDATA||'','claude-pet'):pl==='darwin'?p.join(h,'Library/Application Support/claude-pet'):p.join(h,'.config/claude-pet');
+try{
+  const c=JSON.parse(fs.readFileSync(p.join(d,'config.json'),'utf-8'));
+  const s=c.petState||{};
+  let n='';try{n=fs.readFileSync(p.join(h,'.claude-pet/name.txt'),'utf-8').trim()}catch{}
+  const name=n||'Your pet';
+  const oldH=s.hunger||50;const newH=Math.max(0,oldH-30);
+  const happy=s.happiness||50;const energy=s.energy||50;
+  const exp=(s.exp||0)+5;
+  const stage=exp>=500?'Adult':exp>=100?'Teen':'Baby';
+  const lv=exp>=500?3:exp>=100?2:1;
+  console.log();
+  console.log('🍖 *nom nom* '+name+' happily eats the food!');
+  console.log('📊 Lv.'+lv+' '+stage+' | 🍗 Hunger: '+oldH+'→'+newH+'% | 😊 Happy: '+happy+'% | ⚡ Energy: '+energy+'% | ⭐ EXP: '+exp);
+  console.log();
+}catch{console.log('\n🍖 Your pet has been fed! It looks happy~\n')}
+" 2>/dev/null || echo "🍖 Your pet has been fed! It looks happy~"
+```

package/.claude/commands/name.md

@@ -0,0 +1,28 @@
+Name your Claude Pet!
+
+Give your pet a special name. Usage: `/name Buddy`
+
+```bash
+NAME="$ARGUMENTS"
+if [ -z "$NAME" ]; then
+  if [ -f ~/.claude-pet/name.txt ]; then
+    CURRENT=$(cat ~/.claude-pet/name.txt)
+    echo ""
+    echo "🏷️ Your pet's name is: $CURRENT"
+    echo "To rename, use: /name <new-name>"
+    echo ""
+  else
+    echo ""
+    echo "🏷️ Your pet doesn't have a name yet!"
+    echo "Give it one with: /name <name>"
+    echo ""
+  fi
+else
+  mkdir -p ~/.claude-pet
+  echo "$NAME" > ~/.claude-pet/name.txt
+  echo ""
+  echo "🎉 Your pet is now named '$NAME'!"
+  echo "All interactions will use this name from now on."
+  echo ""
+fi
+```

package/.claude/commands/pet.md

@@ -0,0 +1,29 @@
+Pet your Claude Pet!
+
+Appends a pet event to the pet's event file so your desktop pet reacts with a happy purring animation. Shows current pet status after petting.
+
+```bash
+mkdir -p ~/.claude-pet && echo '{"type":"pet","timestamp":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' >> ~/.claude-pet/events.jsonl
+
+node -e "
+const fs=require('fs'),os=require('os'),p=require('path'),h=os.homedir();
+const pl=os.platform();
+const d=pl==='win32'?p.join(process.env.APPDATA||'','claude-pet'):pl==='darwin'?p.join(h,'Library/Application Support/claude-pet'):p.join(h,'.config/claude-pet');
+try{
+  const c=JSON.parse(fs.readFileSync(p.join(d,'config.json'),'utf-8'));
+  const s=c.petState||{};
+  let n='';try{n=fs.readFileSync(p.join(h,'.claude-pet/name.txt'),'utf-8').trim()}catch{}
+  const name=n||'Your pet';
+  const oldH=s.hunger||50;const newH=Math.max(0,oldH-10);
+  const oldHappy=s.happiness||50;const newHappy=Math.min(100,oldHappy+10);
+  const oldE=s.energy||50;const newE=Math.min(100,oldE+10);
+  const exp=(s.exp||0)+5;
+  const stage=exp>=500?'Adult':exp>=100?'Teen':'Baby';
+  const lv=exp>=500?3:exp>=100?2:1;
+  console.log();
+  console.log('💕 '+name+' purrs happily as you stroke it~');
+  console.log('📊 Lv.'+lv+' '+stage+' | 🍗 Hunger: '+oldH+'→'+newH+'% | 😊 Happy: '+oldHappy+'→'+newHappy+'% | ⚡ Energy: '+oldE+'→'+newE+'% | ⭐ EXP: '+exp);
+  console.log();
+}catch{console.log('\n💕 You petted your pet! It purrs happily~\n')}
+" 2>/dev/null || echo "💕 You petted your pet! It purrs happily~"
+```

package/.claude/commands/play.md

@@ -0,0 +1,29 @@
+Play with your Claude Pet!
+
+Appends a play event to the pet's event file so your desktop pet reacts with an excited playing animation. Shows current pet status after playing.
+
+```bash
+mkdir -p ~/.claude-pet && echo '{"type":"play","timestamp":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' >> ~/.claude-pet/events.jsonl
+
+node -e "
+const fs=require('fs'),os=require('os'),p=require('path'),h=os.homedir();
+const pl=os.platform();
+const d=pl==='win32'?p.join(process.env.APPDATA||'','claude-pet'):pl==='darwin'?p.join(h,'Library/Application Support/claude-pet'):p.join(h,'.config/claude-pet');
+try{
+  const c=JSON.parse(fs.readFileSync(p.join(d,'config.json'),'utf-8'));
+  const s=c.petState||{};
+  let n='';try{n=fs.readFileSync(p.join(h,'.claude-pet/name.txt'),'utf-8').trim()}catch{}
+  const name=n||'Your pet';
+  const hunger=s.hunger||50;
+  const oldHappy=s.happiness||50;const newHappy=Math.min(100,oldHappy+25);
+  const energy=s.energy||50;
+  const exp=(s.exp||0)+5;
+  const stage=exp>=500?'Adult':exp>=100?'Teen':'Baby';
+  const lv=exp>=500?3:exp>=100?2:1;
+  console.log();
+  console.log('🎮 '+name+' bounces around excitedly!');
+  console.log('📊 Lv.'+lv+' '+stage+' | 🍗 Hunger: '+hunger+'% | 😊 Happy: '+oldHappy+'→'+newHappy+'% | ⚡ Energy: '+energy+'% | ⭐ EXP: '+exp);
+  console.log();
+}catch{console.log('\n🎮 You played with your pet! It\\'s so excited~\n')}
+" 2>/dev/null || echo "🎮 You played with your pet! It's so excited~"
+```

package/.claude/settings.local.json

@@ -0,0 +1,41 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(find:*)",
+      "Bash(npx tsc:*)",
+      "Bash(npm run:*)",
+      "Bash(node:*)",
+      "Bash(git status:*)",
+      "Bash(git add:*)",
+      "Bash(git commit:*)",
+      "Bash(wc -l ./src/core/*.ts ./src/main/*.ts ./src/renderer/*.tsx)",
+      "mcp__plugin_oh-my-claudecode_t__state_write",
+      "Bash(npx vitest:*)",
+      "Bash(grep -E \"\\\\.ts$\")",
+      "Bash(mkdir -p ~/.claude-pet)",
+      "Bash(~/.claude-pet/name.txt)",
+      "Bash(~/.claude-pet/events.jsonl)",
+      "Bash(npm link:*)",
+      "Bash(tasklist)",
+      "Skill(update-config)",
+      "Bash(claude-pet)",
+      "Bash(echo \"exit: $?\")",
+      "Bash(jq:*)",
+      "Bash(taskkill //F //IM electron.exe)",
+      "Bash(rm -f ~/.claude-pet/app.pid)"
+    ]
+  },
+  "hooks": {
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "claude-pet",
+            "timeout": 10
+          }
+        ]
+      }
+    ]
+  }
+}

package/.github/workflows/AGENTS.md

@@ -0,0 +1,60 @@
+<!-- Parent: ../../AGENTS.md -->
+<!-- Generated: 2026-03-14 -->
+
+# .github/workflows/
+
+## Purpose
+GitHub Actions CI/CD pipeline for building and publishing platform installers. The single workflow file `build.yml` produces signed and notarized installers for both Windows (NSIS `.exe`) and macOS (DMG + ZIP) and publishes them to GitHub Releases whenever a version tag is pushed.
+
+## Key Files
+| File | Description |
+|------|-------------|
+| `build.yml` | Defines two parallel jobs: `build-windows` (runs on `windows-latest`, produces `.exe` via electron-builder `--win --publish always`) and `build-mac` (runs on `macos-14`, imports code-signing certificate, builds with `--mac --publish always`, then notarizes DMG and ZIP with `xcrun notarytool`). Triggered on `v*` tag pushes and `workflow_dispatch`. |
+
+## Subdirectories
+| Directory | Purpose |
+|-----------|---------|
+| *(none)* | — |
+
+## For AI Agents
+
+### Working In This Directory
+- Trigger: push a tag matching `v*` (e.g., `git tag v1.2.0 && git push --tags`). The workflow can also be triggered manually via `workflow_dispatch` in the GitHub Actions UI.
+- Both jobs use `--publish always`, which uploads artifacts to GitHub Releases using `GH_TOKEN` (automatically provided by `secrets.GITHUB_TOKEN`). The release must already exist or electron-builder will create a draft.
+- The macOS job requires four repository secrets: `MAC_CERTIFICATE_P12` (base64-encoded P12), `MAC_CERTIFICATE_PASSWORD`, `APPLE_ID`, `APPLE_APP_SPECIFIC_PASSWORD`, `APPLE_TEAM_ID`. Without these, the macOS build will fail at the signing step.
+- Notarization uses `xcrun notarytool submit --wait --timeout 10m` directly (not the `@electron/notarize` package used in `scripts/notarize.js`) — these are two separate notarization paths. The CI job notarizes the final DMG/ZIP artifacts; `notarize.js` is the electron-builder `afterSign` hook for the `.app` bundle itself.
+- Windows artifacts are uploaded as `release/*.exe`; macOS artifacts as `release/*.dmg` and `release/*.zip`, both retained for 30 days.
+- Node version is pinned to 20 with `npm` cache enabled. Do not change the Node version without testing compatibility with native modules (`sharp`, `png-to-ico`).
+
+### Testing Requirements
+- Use `workflow_dispatch` to test the full pipeline without pushing a release tag.
+- The Windows job can be validated independently of macOS secrets.
+- Check that `npm run build` succeeds locally on both platforms before pushing a release tag — the CI build mirrors the local build steps exactly (`npm ci`, `npm run build`, then `electron-builder`).
+
+### Common Patterns
+- Publishing pattern: `npx electron-builder --platform --publish always` with `GH_TOKEN` in the environment.
+- Notarization pattern (CI):
+  ```bash
+  xcrun notarytool submit "$FILE" \
+    --apple-id "${{ secrets.APPLE_ID }}" \
+    --password "${{ secrets.APPLE_APP_SPECIFIC_PASSWORD }}" \
+    --team-id "${{ secrets.APPLE_TEAM_ID }}" \
+    --wait --timeout 10m
+  xcrun stapler staple "$FILE"
+  ```
+- Artifact upload: `actions/upload-artifact@v4` with `retention-days: 30`.
+
+## Dependencies
+### Internal
+- Executes `npm ci`, `npm run build`, `npx electron-builder`
+- Reads secrets: `GITHUB_TOKEN`, `MAC_CERTIFICATE_P12`, `MAC_CERTIFICATE_PASSWORD`, `APPLE_ID`, `APPLE_APP_SPECIFIC_PASSWORD`, `APPLE_TEAM_ID`
+- Consumes `build/` assets (icons, installer images) generated by `scripts/make-icon.js`
+
+### External
+- `actions/checkout@v4`
+- `actions/setup-node@v4`
+- `apple-actions/import-codesign-certs@v3`
+- `actions/upload-artifact@v4`
+- Apple Notary Service (`xcrun notarytool`)
+
+<!-- MANUAL: -->

package/.github/workflows/build.yml

@@ -0,0 +1,87 @@
+name: Build Installers
+
+on:
+  push:
+    tags:
+      - 'v*'
+  workflow_dispatch:
+
+permissions:
+  contents: write
+
+jobs:
+  build-windows:
+    runs-on: self-hosted
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+
+      - run: npm ci
+
+      - run: npm run build
+
+      - run: npx electron-builder --win --publish always
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: windows-installer
+          path: release/*.exe
+          retention-days: 30
+
+  build-linux:
+    runs-on: self-hosted
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+
+      - run: npm ci
+
+      - run: npm run build
+
+      - run: npx electron-builder --linux --publish always
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: linux-installer
+          path: |
+            release/*.AppImage
+            release/*.deb
+          retention-days: 30
+
+  build-mac:
+    runs-on: macos-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+
+      - run: npm ci
+
+      - run: npm run build
+
+      - run: npx electron-builder --mac --publish always
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: mac-installer
+          path: |
+            release/*.dmg
+            release/*.zip
+          retention-days: 30

package/AGENTS.md

@@ -0,0 +1,66 @@
+# Claude Mama
+
+## Purpose
+Claude Mama is an Electron desktop mascot widget that monitors Claude Code API usage. It reads the user's OAuth credentials from `~/.claude/.credentials.json` (or platform keychains), polls the Anthropic usage API every 5 minutes, and displays a pixel-art character whose mood (angry / worried / happy / proud) reflects weekly token utilization. The app ships as a frameless, always-on-top, transparent window with no taskbar entry. It supports a quote collection system, badge achievements, share-card generation, custom character skins, and i18n across Korean, English, Japanese, and Chinese.
+
+## Key Files
+| File | Description |
+|------|-------------|
+| `package.json` | npm scripts, dependencies (Electron 40, React 19, electron-store, electron-updater) |
+| `tsconfig.json` | Base TypeScript config shared by renderer |
+| `tsconfig.main.json` | TypeScript config for the main process (CommonJS output to `dist/main/`) |
+| `tsconfig.renderer.json` | TypeScript config for the renderer |
+| `vite.config.ts` | Vite bundler config for the renderer |
+| `vitest.config.ts` | Vitest unit test config |
+| `electron-builder.yml` | electron-builder packaging config for Windows/macOS |
+| `README.md` | User-facing documentation |
+
+## Subdirectories
+| Directory | Purpose |
+|-----------|---------|
+| `src/` | All application source code |
+| `scripts/` | Build-time utilities (icon generation, notarization) |
+| `build/` | Static assets consumed by electron-builder (icons, installer images) |
+| `docs/` | Design specs, planning documents, reference images |
+| `.github/workflows/` | CI/CD pipeline for cross-platform builds and releases |
+| `dist/` | Build output (gitignored) |
+| `release/` | Packaged installers output (gitignored) |
+| `node_modules/` | Dependencies (gitignored) |
+
+## For AI Agents
+
+### Working In This Directory
+- The project uses **two separate TypeScript compilation targets**: `tsconfig.main.json` compiles the Electron main process to `dist/main/` as CommonJS; Vite compiles the renderer to `dist/renderer/`.
+- Run `npm run dev` to start in development mode (Vite dev server + Electron). Run `npm run build` for a full production build before packaging.
+- `package.json` `"type": "commonjs"` means all `.js` files are CommonJS by default; the renderer uses ESM via Vite.
+- Never import Electron APIs from `src/core/` or `src/shared/` — these layers must stay pure Node/browser-compatible.
+- The entry point for the packaged app is `dist/main/main/main.js`.
+
+### Testing Requirements
+- Run `npm test` (vitest) to execute all unit tests in `src/core/__tests__/`.
+- Tests cover: mood engine, quote triggers, badge triggers, quote collection, contextual messages.
+- There are no integration or E2E tests; test only via `vitest run`.
+- When adding new core logic, add a corresponding test in `src/core/__tests__/`.
+
+### Common Patterns
+- Mood thresholds: `<15%` = angry, `15–50%` = worried, `50–85%` = happy, `≥85%` = proud.
+- Error states use `MamaErrorExpression`: `'confused'` (API error) or `'sleeping'` (no credentials).
+- IPC channel names are defined as constants in `src/shared/types.ts` (`IPC_CHANNELS`).
+- Locale detection happens at module load time via `detectLocale()` in `src/shared/i18n.ts`.
+- All user preferences are persisted through `electron-store` (accessed via `getStore()` in `src/main/ipc-handlers.ts`).
+
+## Dependencies
+### Internal
+- `src/` → `build/` (icons referenced in `electron-builder.yml`)
+- `scripts/make-icon.js` reads from `docs/images/character.webp` and writes to `build/`
+
+### External
+- `electron` ^40 — desktop shell
+- `react` / `react-dom` ^19 — renderer UI
+- `electron-store` 8.2.0 — persistent settings
+- `electron-updater` ^6 — auto-update via GitHub Releases
+- `auto-launch` ^5 — system startup registration
+- `vite` ^7, `vitest` ^4, `typescript` ^5.9 — build and test toolchain
+- `sharp`, `png-to-ico` — icon generation (dev only)
+
+<!-- MANUAL: -->

package/LICENSE

@@ -0,0 +1,15 @@
+ISC License
+
+Copyright (c) 2025 scm1400
+
+Permission to use, copy, modify, and/or distribute this software for any
+purpose with or without fee is hereby granted, provided that the above
+copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH
+REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
+AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
+INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
+LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR
+OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
+PERFORMANCE OF THIS SOFTWARE.