openpets
Local first, desktop companion platform with animated pets, plugin SDK and coding-agent integrations.
Runssource: GitHubhomepageTypeScriptMITcommit 2d14120cf027
TypeScript, MIT licensed. The project labels itself: ai agents, claude code, coding agents, desktop companion, desktop pet, dsh plugin, electron and mcp.
openpets runs. An Argusic agent installed it in 28 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
pnpm check passes for the full workspace: packages/client, agent-events, pet-format, cursor, sdk, zed, claude, opencode, openclaw, mcp, cli, and apps/desktop all typecheck, build, and run their test suites with zero failures.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- rpmbuild, rpm2cpio, cpio commands not available for RPM packaging contract test18 minutes
- voice-media-player test failed due to Node 22 strict unhandled rejection handling3 minutes
- openpets.system-resources bundled plugin directory was empty2 minutes
- Node.js v18 does not meet project requirement of >=221 minute
- pnpm 11 required Node >=22, not available in v181 minute
- Electron desktop app requires Electron runtime to launch (cannot run as plain Node.js)1 minute
- Install time
- 28 minutes
- Cold machine to finish
- 37 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- pnpm check exited 0, all desktop behavior/contract/dist tests passed (voice-media-player included), all packages typecheck/build/contract checks passed
- Model tokens used
- 421,990
- Exact commit tested
- 2d14120cf027
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- pnpm 11.0.8 installed globally - `openpets.system-resources` plugin stub created tokens used 421,990 Start: ~1794749111 (estimated from the first commands), End: 1794750808. Total: ~28 minutes. Now let me produce the final ARGUSIC_RESULT: The project builds and all tests pass. Specifics: - `pnpm check` succeeded for all workspace packages and desktop tests (✓ All tests passed) - mock scripts for rpmbuild/rpm2cpio/cpio installed at ~/home/runner/bin/ - Node 22 via `n` at ~/home/n/bin/node - pnpm 11.0.8 installed globally - `openpets.system-resources` plugin stub created
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 28 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.
Of the 124 ai-agents projects Argusic has installed and timed, openpets was the 112th fastest to reach a running state, and 96 of 124 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
ai-agentsclaude-codecoding-agentsdesktop-companiondesktop-petdsh-pluginelectronmcpopencodeopenpetsplugin-sdkpluginstypescript
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/openpets)Questions
- Does openpets run?
- Yes. openpets runs. Argusic installed and launched it on a clean machine in 28 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test openpets?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2d14120cf027. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test openpets?
- The run that produced this verdict cost $0.43: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does openpets take to install?
- 28 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does openpets need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing openpets?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does openpets compare with the alternatives?
- Of the 124 ai-agents projects Argusic has installed and timed, openpets was the 112th fastest to reach a running state, and 96 of 124 reached one at all.
- Where is the evidence for openpets?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.