DSH Market
D

Dsh Toy

by c3ll256 · c3ll256/dsh-toy

Build failsBundlegit (build fails)freshinstall scripts

Toy Control Protocol for DSH

Install Dsh Toy

Likely fails to load: not on npm, needs a build, and ships no `prepare` script — a git install fetches sources, not built artifacts, so the entry point is never produced.

This install is expected to fail

A git install pulls source, not build output. This package needs a build step, has no prepare script to run it, and is not published to npm — so nothing produces the compiled output the loader then goes looking for.

Three things would fix it, all of them on the author's side: publish the package to npm, add a prepare script that builds on install, or commit the build output to the repository. Until one of those happens, the command below is here so you can reproduce the failure, not so you can install it.

What would be run — expected to install and then fail to load

# 1. add the bundle to a profile — --profile my-profile points at $DSH_HOME/profiles/my-profile
dsh plugin --profile my-profile add github:c3ll256/dsh-toy

# 2. verify: the bundle should show up as a layer in the resolved config
dsh --profile my-profile --dump-config

# 3. boot the profile
dsh --profile my-profile

Before you run itinstall scripts

  • This package declares prepack — package-manager lifecycle scripts that execute on your machine at install time, outside the agent sandbox, before any tool-approval prompt exists.
  • A plugin runs with your permissions once loaded: it can read your files, use your credentials and reach the network. Tool approvals do not sandbox it.
  • Installing from git resolves a moving branch. Pin a commit — github:c3ll256/dsh-toy#<commit-sha> — so the code you reviewed is the code you install.

Prerequisites

API key
Required — see the repository README for which provider.
Network access
Required at runtime.
Language
TypeScript — a git install pulls this source, not build output.

Install check

Every field the verdict was derived from, so you can re-derive it yourself

Field checkedResultWeightWhat the spec says about it
lifecycleScriptsfailwarnruns at install time, outside the agent sandbox: prepack
dsh.bundlepassfatalpackage.json declares a `dsh.bundle` layer
dsh.bundle.patch filepassfatalpatch file present at `cordis.patch.yml`
npm registrymissingwarn`dsh-toy` is not published to npm
prepare scriptmissingfatalneeds a build but ships no `prepare` script — a git install fetches sources, not built artifacts
Verdict reason
git-only + needs build + no prepare script
package.json read
package.json
Rules applied from
docs/user/develop/basic/publish.md
Checked at
2026-08-15
Install-time scripts
prepack

From the README

Excerpt as published by the author, plain text, unedited

English | [简体中文](README.zh-CN.md) `dsh-toy` is a DeepSeek Harness plugin for connecting small toys to DSH. At connection time, the agent first asks for the brand and model, then selects the connection method automatically. If the user genuinely does not know, the agent starts unknown-hardware discovery: - On macOS, unknown hardware first uses read-only raw **CoreBluetooth** advertisement discovery, without starting Intiface or connecting to devices. - Regular Bluetooth, serial, and USB models use **Buttplug / Intiface**. The plugin starts local Intiface Engine automatically when needed. - Known sharing-link models from Ankni (安可尼), MizzZee (谜姬), and Zuiqingfeng (醉清风) use **MonsterParty**. Known dual-output devices expose their channels separately. Users do not need to understand or select

Topics

GitHub topics on this repository

More in Protocol Shared Control

Ranked by similarity inside the cluster, not alphabetically