What breaks without openclaw demo project
No real state-persistence example. Abstract docs. Learning on production projects.
→
Hands-on state persistence learning × fun Tamagotchi demo ÷ 15-minute setup ÷ no production risk = deep OpenClaw skill fast.
Security check — openclaw demo project
Privacy score: 7/10 — accesses connected platform APIs only.
Lock it: review OAuth scopes before install, confirm OpenClaw ≥1.1; any platform adapter; local storage for state compatibility.
Quick start — openclaw demo project in 15–30 minutes
Setup time: 15–30 minutes
!
You need:
- OpenClaw core
- any messaging platform adapter
Install the package:
git clone https://github.com/turmyshevd/openclawgotchi
cd openclawgotchi && npm install
npm start
3
Configure your preferred adapter in .env
5
Send 'adopt' to create your pet
6
Feed, play, and check on your pet via chat commands
Compatibility & status
Works with: OpenClaw ≥1.1; any platform adapter; local storage for state
beginner
Last updated: Aug 2025
★ 285 on GitHub
MIT
Official docs →
View on GitHub →
FAQ — openclaw demo project
Does my pet survive a bot restart?
Yes — state is persisted to disk via openclaw-local-memory.
Can multiple users have their own pets?
Yes — state is namespaced per user ID.
Is this production-grade code?
It's a demo — review before using patterns in production.