Foreword

In DSH’s plugin integration approach, a capability module can enter the host session as a plugin. The positioning of dsh-airp is: the AIRP engine on DeepSeek Harness, containing the deep module WorldKernel and the shallow Host adapter.

It treats the world package as directory data, rather than treating the package itself as plugin code. Below is an introduction to its positioning, core capabilities, installation steps, and a few reproducible use cases.

What is this

dsh-airp is the AIRP engine on DeepSeek Harness. The repository path is clarkzhao/dsh-airp, and the license is MIT.

Based on verified information, it revolves around the world package: the world package is data, not plugin code; the engine only recognizes whether there is a valid pack.yaml in the directory.

Core Capabilities

The capabilities listed below are verified facts:

  • WorldKernel.turn / match: Identification, narrative facts, GM, retrieval.
  • Pack.load / validate / catalog: YAML index + Markdown details; sources include bundled, ~/.dsh/airp-packs, and custom paths.
  • Optional stage airpStage: /airp-media turns local maps into same-origin absolute http(s) URLs, embedding the narrator in dialogue. It does not generate images itself, nor does it bind grok-image.
  • The world package is data, not plugin code; the engine only recognizes whether there is a valid pack.yaml in the directory.
  • Tool names must match ^[a-zA-Z0-9_-]+$.

Installing to DSH web profile

First prepare the local repository path, then install it to the web profile:

dsh plugin --profile web add /path/to/dsh-airp

/path/to/dsh-airp in the command is a placeholder for the local path.

After the above steps, copy the presets:

cp -R presets/airp-play ~/.dsh/.agent-presets/airp-play
cp -R presets/airp-author ~/.dsh/.agent-presets/airp-author

When copying presets, do not include tool-cordis, and do not mount play-mask in the play preset. Verified instructions state that tools.restrict is still empty during mounting, and New Session will fail.

Typical Usage

Consumer Path

airp-play is used for selecting the world package at the start. With the steps above, you can select a world package from the initial phase.

Creator Path

The path for airp-author is: use pack_interview to get 8 questions first, then go through pack_scaffold, pack_validate, and pack_open_play.

Local Validation

User packages are recommended to be written to ~/.dsh/airp-packs/ because the host plugin writes to disk without going through the agent sandbox. The sandbox can only write to the workspace.

When validating a package:

npm run pack:validate -- ~/.dsh/airp-packs/my-pack

pack_open_play will not hot-load the current session. Existing output cannot switch presets; you need to open a new airp-play and paste the path.

Use Cases and Notes

dsh-airp is suitable for using AIRP world packages in the DSH web profile, or for those who need to create and validate world packages.

Note the following points:

  • The plugin runs with the permissions of the current dsh process; you should check the source code and license before installing.
  • The repository declares the license as MIT, and source code can be viewed from the GitHub repository.
  • Do not PR community packages into this repository’s packs/ directory, unless it is intended to become the next official demo.
  • Use repository templates for Issues; template categories include pack, authoring, and engine.

Conclusion

dsh-airp splits AIRP capabilities into the deep module WorldKernel and the shallow Host adapter, and allows world packages to be validated and used in the form of directory data. Performing local validation first, and then opening a new airp-play session, is a more reliable implementation order.

Plugin directory name: clarkzhao/dsh-airp

GitHub repository: https://github.com/clarkzhao/dsh-airp