MIT-licensed, local-first desktop companion for coding agents — an animated pet plus a plugin SDK, wired to agents via an optional MCP server so they can react on your desktop.
DSH integration
Compatible
Author-claimed
Safety audit
Unaudited
Last verified
2026-09-04
License
MIT
01What can it help you accomplish?
Put an animated companion on your desktop that plugins turn into a focus buddy, reminder system, tiny game, launcher, or coding-agent sidekick.
Animated desktop pets that idle, wander, and react; an official plugin lineup (focus timers, reminders, mood check-in, launcher, magic 8-ball, and more) bundled with the host.
Developers and coding-agent users who want a local, animated desktop companion alongside their workflow — no AI account or setup required to use the app.
Let a coding agent drive your desktop pet's reactions over MCP.
Standard MCP tools (openpets_status, openpets_react, openpets_say) that trigger animations, change status, and display speech bubbles locally on your machine.
Coding-agent users (Claude Code, OpenCode, Cursor, Pi, or any MCP client) who want their agent visible and reactive on the desktop without leaking prompts, code, paths, logs, or secrets.
02How to install into DeepSeek Harness
Prerequisites
- Desktop app for macOS (Apple Silicon / Intel), Windows (x64), or Linux (x86_64 AppImage), downloaded from GitHub Releases
- An MCP-capable coding agent if you want agent-driven reactions (optional — the desktop app works fully without any agent)
Installation steps
- 01
Download the OpenPets desktop package for your operating system from GitHub Releases and launch it; a pet appears immediately with no agent setup required.
- 02
Optional — to let an agent drive the pet: add OpenPets as an MCP server in your agent's configuration (e.g. `npx -y @open-pets/mcp@latest` over stdio).
$ npx -y @open-pets/mcp@latest
Verify the integration
- Run `npx @open-pets/cli doctor` to check whether the desktop app is reachable and whether agent/MCP integrations are installed, need an update, or are broken.
03DSH integration and capability boundaries
Connects to coding agents through an optional local MCP server: OpenPets exposes standard MCP tools that any MCP-capable client (Claude Code, OpenCode, Cursor, Pi, etc.) can use to drive the desktop pet's reactions locally.
MCP agent integration
a configured coding agent (Claude Code, OpenCode, Cursor, Pi, or any MCP client)→standard MCP tools — openpets_status, openpets_react, openpets_say — that trigger animations, change status, and show speech bubbles locally
installs OpenPets MCP, memory instructions in `~/.claude/CLAUDE.md`, and hooks in `~/.claude/settings.json` (Claude Code)registers OpenPets as a stdio or TCP MCP server in the agent's configurationLocal-first desktop app with plugin SDK
the bundled official plugin lineup, or your own plugins built on the v3 SDK→an animated desktop companion (focus buddy, reminder, launcher, tiny game) running fully locally; a plugin SDK (`ctx`) to hook into pets, panels, events, audio, notifications
Local privacy & safety model
plugin network calls and dynamic AI speech→SSRF/private-host guards, dynamic-content sanitization, and explicit opt-in for sensitive permissions
network fetch is limited to developer-declared hostnames and blocked from local network/private IP accessfeatures accessing clipboard, microphone, or dynamic AI responses are off by default and require explicit user opt-in
04Who is it for? When not to use it?
Good for
- Developers and coding-agent users who want a local, animated desktop companion alongside their workflow — no AI account or setup required to use the app.
- Coding-agent users (Claude Code, OpenCode, Cursor, Pi, or any MCP client) who want their agent visible and reactive on the desktop without leaking prompts, code, paths, logs, or secrets.
05Compatibility, maintenance and safety notes
- macOS builds may be unsigned and can trigger a security warning; if macOS blocks execution, remove the quarantine flag via terminal (`xattr -dr com.apple.quarantine /Applications/OpenPets.app`).
- Sensitive features (clipboard, microphone, dynamic AI speech) are off by default and require explicit user opt-in; plugin permissions must be declared in the manifest and approved at install.
- Plugin network connections are restricted to approved domains and blocked from local network/private IP access; any dynamic AI-speech text runs through strict local filters to redact paths, URLs, secrets, or multiline code.
MIT licensed; actively maintained (latest release v3.5.0 on 2026-09-02); README describes it as local-first with no accounts or central AI server.
06Frequently asked questions
How do I connect OpenPets to DeepSeek Harness?
OpenPets connects to coding agents through its optional local MCP server (`@open-pets/mcp`). If DeepSeek Harness can act as an MCP client, register OpenPets as an MCP server in its configuration (`npx -y @open-pets/mcp@latest` over stdio); the agent can then trigger pet reactions locally. The README lists Claude Code, OpenCode, Cursor, and Pi as supported MCP clients — it does not name DeepSeek Harness explicitly.
Do I need an account or API key to run OpenPets?
No. The desktop app is local-first with no accounts, sign-ups, or central AI server; the pet works immediately after install. Only agent-driven features use connections you configure yourself.
What can the desktop pet actually do?
It shows an animated companion that idles, wanders, and reacts, plus an official plugin lineup (focus timers, reminders, mood check-in, launcher, magic 8-ball, and more). Plugins can turn it into a focus buddy, reminder system, tiny game, launcher, or coding-agent sidekick.
Is my code or prompts exposed to the pet?
No. MCP clients drive local pet reactions "without exposing prompts, code, paths, logs, or secrets in speech bubbles." Sensitive permissions (clipboard, microphone, dynamic AI speech) are off by default and need explicit opt-in.
How do I verify the integration is working?
Run `npx @open-pets/cli doctor` — it reports whether the desktop app is reachable and whether agent/MCP integrations are installed, need an update, or are broken, and the command exits non-zero only when an integration is broken.
07Related DSH workflows
ruflo
by ruvnet
🌊 The original agent meta-harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
reactive-resume
by amruthpillai
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
everos
by evermind-ai
One portable memory layer for every AI agent: local-first, Markdown-native, user-owned, and self-evolving across apps, tools, and workflows.
yao
by yaoapp
✨ All your agents and workspaces in one place, on every device you own. Track tasks on a board, accessible from desktop, mobile, browser, or API. Self-hosted.
08Data and sources
OpenPets provides an optional local MCP (Model Context Protocol) integration layer.
When you configure an agent, OpenPets exposes standard MCP tools. The agent can trigger animations, change status, and d…
MCP clients can drive local pet reactions without exposing prompts, code, paths, logs, or secrets in speech bubbles.
This page is generated from the project’s public documentation, repository metadata and a structured parse of DSH Plugins; last verified on 2026-09-04. Found an error? Submit a correction.
Best DeepSeek Harness Plugins
Twelve plugins worth installing first — picked from the whole catalog, across every category.