Skip to content

About

PhyAgentOS plugin for deepseek harness

Resources

Security policy

Stars

2 stars

Watchers

0 watching

Forks

Repository files navigation

English | 中文

PhyAgentOS-DSH-Plugin

DeepSeek Harness (DSH) plugins and tools for installing, running and managing Forge skills: Dora dataflows, node artifacts and Gateway Tool APIs.

User guide · Release guide · npm packages · GitHub Releases · npm package management — maintainers

Packages

All five packages are public on npm and support independent, tag-triggered releases through GitHub Actions trusted publishing.

Package Purpose Installed with the DSH bundle?
@x-era/dsh-forge DSH bundle and plugin entry point Yes
@x-era/dsh-forge-skill Skill provider, management tools and built-in instructions Yes, dependency
@x-era/forge-core Manifests, registry, verified installation, runtime and Tool API client Yes, transitive dependency
@x-era/forge-cli Standalone forge command No, optional
@x-era/forge-mcp MCP stdio server for other agent clients No, optional

The npm management page requires an npm account with organization permissions. Public package pages are available to consumers.

Quick start: DSH Web

Use Node.js >=24.9.0 for the tested DSH host. If dsh is not installed:

node --version
npm install --global @deepseek-ai/dsh@0.2.2-rc.1
dsh --version

Install into the profile you will launch:

dsh plugin --profile web add @x-era/dsh-forge
dsh web

For a DSH source checkout, run these commands in the deepseek-harness repository:

pnpm dsh plugin --profile web add @x-era/dsh-forge
pnpm dsh web

dsh web selects the web profile. Installing with --profile dev only affects dev; it does not enable the plugin in web. Restart an already-running profile after adding the bundle and open a new conversation.

Expected capabilities: forge-usage, forge-skill-development and forge_* management tools. This installs the plugin, not a robot skill, Dora or hardware/model dependencies. See the user guide for checks and configuration.

Validation baselines: npm DSH 0.2.2-rc.1; Web plugin registration also checked with a DSH 0.2.2-rc.2 source checkout.

First-time machine setup (in natural language)

After installing the plugin and opening a new DSH conversation, you do not need to install Dora manually or hand-edit cordis.patch.yml. Run these directly in chat:

  1. Check: “I just installed the Forge plugin — check what this machine is missing to run Forge.” (forge_environment_check)
  2. Bootstrap: “Bootstrap the Forge environment: install Forge 1 dora 0.4.1 and Forge 2 dora1 1.0.1 into ~/.dsh/forge/support/ and re-verify (add a PyPI mirror URL or local binary paths if needed).” (forge_environment_setup)
  3. Configure safely: “Show the current Forge config in the web profile, and safely update models.root or registry.url with a backup.” (forge_config_read / forge_config_write)

See the deployment guide for mirror, offline-binary, and rollback examples.

Usage examples

In DSH, ask for the operation directly:

Goal Example request Main tool
Installed skills “List installed Forge skills and their runtime states.” forge_skill_list
Environment “I just installed the plugin — check whether this machine can run Forge.” forge_environment_check
Bootstrap host “Install Forge 1 dora 0.4.1 and Forge 2 dora1 1.0.1 into ~/.dsh/forge/support/ and verify.” forge_environment_setup, forge_config_write
Local models “Search local Forge models under ~/.dsh/forge/models and inspect or verify sam3.” forge_model_search, forge_model_info, forge_model_verify
Available skills “Search the Forge registry for robot simulation skills.” forge_skill_search
Choose a profile “Inspect robot-control-sim and list its profiles and requirements.” forge_skill_inspect after installation
Install “Install robot-control-sim with its nodes and report installation progress.” forge_skill_install, forge_install_status
Start simulation “Check robot-control-sim / mujoco-piper, then start it if preflight passes.” forge_skill_doctor, forge_runtime_start
Read robot state “Call sim.get_robot_info on the running robot-control-sim skill.” forge_tool_call
Stop “Stop the robot-control-sim runtime and confirm its state.” forge_runtime_stop, forge_runtime_status

The registry currently provides robot-control-sim / mujoco-piper. Inspect its current requirements and platform support before starting it.

For a shell workflow, install the optional CLI first:

npm install --global @x-era/forge-cli
forge env
forge search robot
forge list
forge install robot-control-sim --wait
forge inspect robot-control-sim
forge doctor robot-control-sim --profile mujoco-piper
# Continue only if the required binaries, environment and platform checks pass.
forge start robot-control-sim mujoco-piper
forge status robot-control-sim
forge call robot-control-sim sim.get_robot_info
forge stop robot-control-sim

CLI output is JSON. Action/session acceptance is not completion: use forge_invocation_read in DSH/MCP to check an invocation; do not repeat an action with an unknown result. See workflow details.

Configuration

Set the forge-skill row in $DSH_HOME/profiles/web/cordis.patch.yml (default home: ~/.dsh):

- id: forge-skill
  config:
    registry:
      url: https://paos-resource-platform.dev.x-era.com
      tokenEnv: DSH_FORGE_REGISTRY_TOKEN
    runtime:
      dora: /path/to/dora
      dora1: /path/to/dora1

Replace the executable paths with those required by your skill. DSH_FORGE_HOME, DSH_FORGE_REGISTRY_URL, DSH_FORGE_DORA and DSH_FORGE_DORA1 provide environment defaults. See configuration and data for precedence, authenticated registries and the optional console.

Develop and release

git clone https://github.com/PhyAgentOS/PhyAgentOS-DSH-Plugin.git
cd PhyAgentOS-DSH-Plugin
pnpm install --frozen-lockfile
pnpm test
dsh plugin --profile web add file:/absolute/path/to/PhyAgentOS-DSH-Plugin/bundle

Use the explicit file: form and reinstall after rebuilding. The DSH host is a separate project. DSH_CHECKOUT=/path/to/deepseek-harness pnpm check:dsh checks the declared upstream API baseline; a changed hash alone does not establish runtime compatibility.

Release one package by updating its own manifest, merging a personal-fork PR into main, then creating its matching tag, such as forge-cli/v0.1.2. A new remote tag triggers tests, npm publishing and a GitHub Release with the tarball. Upload processing is polled every 15 seconds for up to approximately 15 minutes.

See the release guide for all five version files, tag naming, OIDC setup, GitHub-page steps and recovery. Maintainers can use npm package management.

Documentation

Guide English 中文
Installation, usage, CLI/MCP and troubleshooting User guide 使用手册
Independent releases, tags and npm authorization Release guide 发布手册

Additional guides in Chinese: deployment · operations · security · skill development · portability.

License

MIT. See LICENSE.

About

PhyAgentOS plugin for deepseek harness

Resources

Security policy

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages