zoahdev/dsh-pet-evolve
The pet that grows with your DeepSeek Harness agent: stage evolution from real signals, agent-state mirroring, one-click growth share cards. Zero dependencies.
Listed
0
Fun
Bundle verified
What it does
The pet that grows with your agent: 5 evolution stages earned from real signals (verified rules, completed sessions, tool calls, compactions), agent-state mirroring, and one-click growth share cards. Zero dependencies, 100% local.
Best for
- Users who want a local, gamified view of agent activity and progress across five pet evolution stages.
- Profiles where completed sessions, tool calls, compactions, or verified rules should contribute visible growth signals.
- People who want locally generated growth cards or a lightweight focus-timer companion without telemetry.
Not ideal for
- Operational monitoring, auditing, or productivity measurement that requires formal reports rather than a gamified representation.
- Workflows that do not want the plugin reading the local session logs or rule files explicitly supplied to it.
- Users seeking cloud synchronization or multi-device state sharing; the documented data model is fully local.
README
dsh-pet-evolve
The pet that grows with your DeepSeek Harness agent. Not a static sprite - a living companion that levels up from real agent signals, mirrors your agent’s state, and mints shareable growth cards.
Zero dependencies · all data stays on your machine · works standalone or inside DSH.
Why this is different
Pet galleries show you sprites. This is the opposite: your pet’s body is earned.
| petdex / whale-girl style | dsh-pet-evolve | |
|---|---|---|
| Sprites | static gallery | 5 evolution stages, drawn live on canvas |
| Agent awareness | none | mirrors working / done / failed / idle from real session events |
| Growth source | nothing | verified rules (dsh-rule-evolve), completed sessions, tool calls, compactions |
| Share | screenshots | one-click 1200×630 growth card PNG |
| Data | varies | 100% local, zero telemetry |
Quick start
# standalone (no install)
npx dsh-pet-evolve
# open http://127.0.0.1:4173
# bind real DSH signals from a profile
npx dsh-pet-evolve --profile ~/.dsh/profiles/web
# also count dsh-rule-evolve evolution rounds (+5 XP each)
npx dsh-pet-evolve --profile ~/.dsh/profiles/web --evolution ~/.dsh/profiles/web/EVOLUTION.md
# headless growth report
npx dsh-pet-evolve --report
Feed and play with the pet directly; when bound to a profile, it also earns XP from:
-
rule_verified— rules in the profile rule library (dsh-rule-evolve compatible) -
session_completed— finished sessions in the profile -
tool_call— tool activity in session logs -
compaction— compaction summaries
DSH plugin mode
dsh plugin --profile web add github:zoahdev/dsh-pet-evolve
The host plugin starts the pet server bound to the profile (port 4173 by default). The lib/ entry is committed, so no build step is needed at install time.
Evolution
Egg → Baby → Teen → Adult → Legend. One level per 100 XP; stage thresholds at 300 / 800 / 1600 / 3000. See docs/evolution-stages.md.
Development
node --test engine adapter # engine + adapter tests
node scripts/build-check.mjs # artifact integrity
node scripts/pet.mjs # local pet
Privacy
The pet reads local files only (session logs and rule files you point it at) and never sends anything anywhere. The share card is generated in your browser.
Roadmap
- Evolution engine + tests
- DSH session/rule adapter + tests
- Canvas pet + interactions + share card
- CLI + zero-dependency server + DSH plugin wrapper
- Multi-pet skins (whale / cat / robot / ghost)
- Focus-timer productivity mode (+5 XP on completion)
- Awesome list entry + marketplace listing (PR #623)
- Live demo page (waiting on a dedicated demo domain)
- Sync with dsh-rule-evolve evolution logs (+5 XP per round)
License
MIT
Frequently Asked QuestionsFAQ
Use the verified command dsh plugin --profile default add github:zoahdev/dsh-pet-evolve in a DSH-enabled shell. The command resolves the public package metadata and keeps the plugin attached to the catalog identity shown on this page.
Compatibility follows the bundle and profile status shown above. If a profile is not detected, keep the plugin disabled there and check the repository documentation before enabling it in production.
The GitHub link and activity metadata are the source of truth for releases and maintenance. Revisit this page after a new release to confirm the catalog has observed the latest version.