Repository navigation
Releases
v0.1.4 — Better development guidance and compatibility checks
dsh-developer 0.1.4 brings clearer development guidance and stronger checks against upstream DSH changes.
- Turn vague ideas into useful plugins. Shared guidance for DeepSeek and GPT now makes intent, design tradeoffs, maintainable implementation and independent behavior checks explicit. Essential guidance stays in the main skill, including during repairs.
- Catch API drift before running. DSH-facing JavaScript is checked against upstream TypeScript declarations, including the actual dependency graph of each tested runtime. Installation still needs no build step.
- Navigate and set up projects more smoothly. Clearer installed-package lookups, missing-build hints, corrected example paths and Windows installer handling reduce common development friction.
- Trust verification results more. Native cases reject numeric values that JSON transport would silently change. Source audits handle growing files within fixed budgets, recognize directly audited context helpers, and cover more loader and assignment cases.
Reviewed runtimes: DSH 0.1.5-rc.2 and 0.1.6-alpha.2. Local validation passed 890 tests, with 45 optional integrations skipped. The release archive passed native package-identity, source-audit and knowledge checks in both headless and Web profiles on both runtimes. Browser opening was disabled.
Install or update in DSH Web:
dsh plugin --profile web add 'github:builtin-pb/dsh-developer#v0.1.4' --ignore-scriptsRestart DSH after installation. The attached archive and SHA256SUMS provide the same release without build scripts.
All 18 CI jobs passed on both the release commit and the v0.1.4 tag, including Windows, macOS and Ubuntu checks and native development against npm latest, next and alpha.
Post-publication checks: the public Git tag and archive URL both installed version 0.1.4 into fresh Web profiles with scripts disabled. All 137 packaged files matched the tested artifact. Each publicly installed CLI passed the three native Web cases; all disposable profiles were removed. The downloaded archive matched the published SHA256SUMS and tested bytes.
v0.1.3 — Audit plugins with images and fonts
dsh-developer 0.1.3 fixes repository audits failing on images and fonts. Adding our own PNG logo exposed the bug: the scanner treated every file as UTF-8 source.
- Doctor, profile preflight, upstream impact, source migration and compatibility checks now accept recognized PNG, JPEG, GIF, WebP, ICO, WOFF, WOFF2, TTF and OTF assets.
- Asset bytes count toward snapshot limits and freshness fingerprints. Changing an image invalidates the audit just like changing source.
- Compressed asset data no longer triggers the text-only entropy heuristic. Explicit credential markers are still checked; assets are not decoded or treated as executable source.
- Isolated Build/Apply transfers retain their existing UTF-8-only contract. The amber-wrench logo is included in both READMEs.
Validation: 779 local tests passed, with 33 optional integrations skipped. Static Doctor and real DSH 0.1.5-rc.2 Web preflight passed. Clean-profile install/uninstall checks passed on both reviewed DSH 0.1.5-rc.2 and 0.1.6-alpha.1. The packed plugin passed all three native cases in both Web and headless profiles on rc.2: the real PNG, asset evidence and rejection of binary executable source.
All 18 CI jobs passed on both main and the v0.1.3 tag, including Windows, macOS and Ubuntu checks and native development against npm latest, next and alpha.
Install or update in DSH Web:
dsh plugin --profile web add 'github:builtin-pb/dsh-developer#v0.1.3' --ignore-scriptsRestart DSH after installation. The attached archive and SHA256SUMS provide the same release without build scripts.
Post-publication checks: the public Git tag and archive URL both installed version 0.1.3 into fresh Web profiles with scripts disabled and identical logo bytes. The public archive matched the tested archive and checksum. The publicly installed CLI also passed all three native Web asset cases against that download.
v0.1.2 — Current DSH contracts and smoother development
dsh-developer 0.1.2 improves the everyday plugin-development loop and updates the reviewed runtime contracts to DSH 0.1.5-rc.2, with 0.1.6-alpha.1 as the advisory target.
- Preview a plugin against a selected workspace, reload Host modules through native DSH watchers, and verify tools through a real workspace-bound Agent.
- Preserve completed verification results when later cases fail or hang. Diagnose startup and case errors with bounded, credential-protected output, and preserve project-script exit status.
- Follow source instructions and installed dependencies in their actual package context. Refresh the typed examples, Client contracts, profile checks and exact-byte hook inventories.
- Repair Mac isolated-tool result serialization and recovery-journal path handling. Concurrent workspace edits remain protected, with recovery retained when rollback cannot be verified.
- Close development tasks with a brief reflection on friction. Ask whether to report a product problem, then draft, sanitize and submit only after consent.
Validation: 773 local checks passed, with 33 optional integration checks skipped. The release archive passed static Doctor and both native Web knowledge-tool cases on DSH 0.1.5-rc.2. Prior exact-runtime review also exercised Apple isolation and native Build/Apply recovery; these do not establish every host or arbitrary model-generated project.
All 18 CI jobs passed on the release revision, including native development on Windows, macOS and Ubuntu across npm latest, next and alpha. Isolated execution still requires admission on the actual host. Native Host reload may race an old asynchronous disposer; plugins holding exclusive resources need an explicit lifetime strategy or a server restart.
Install into DSH Web:
dsh plugin --profile web add 'github:builtin-pb/dsh-developer#v0.1.2' --ignore-scriptsRestart DSH after installation. The attached ready-to-load archive and SHA256SUMS provide the same release without build scripts.
Post-publication checks: the public Git tag and release-archive URL both installed version 0.1.2 into fresh Web profiles with scripts disabled. The downloaded archive matched SHA256SUMS, and both native knowledge cases passed from the public Git-tag installation.
A real Chrome Computer Use check ran the installed development CLI against the downloaded archive with a preselected disposable workspace. Its Web Doctor command visibly returned PASS for a static workspace audit; this was a keyless command check, not an autonomous model trial. Use DSH's authenticated launch URL for initial browser access. On DSH 0.1.5-rc.2, commands in an otherwise empty session can leave their results hidden; running the built-in /goal once revealed the result. This existing upstream display workaround remains applicable.
v0.1.1 — Native development and release readiness
This patch fixes development and cleanup failures found during independent code review and fresh tool-plugin and Web-panel development trials.
- Follow imports from the actual consuming package, including nested installed versions, and account for knowledge reads within one budget.
- Let verbose builds finish with bounded, protected log tails; preserve cancellation causes and report verification failures accurately.
- Use owned temporary pnpm stores, empty archive-preview workspaces and one-shot profile loading. Require all enabled development entries to activate, preserve protected startup diagnostics, and report incomplete shutdown. Improve POSIX worker cleanup without claiming equivalent Windows post-exit cleanup.
- Make UI setup instructions work after profile installation, check the calling Agent’s tool scope, and accept native browser references after navigation.
- Recognize native Connection Fetch routes while requiring exact-runtime evidence for authentication.
- Repair nested directory replacement, early disposal rejection, and preparation-cancellation cleanup in isolated Apply.
- Keep release metadata consistent and update the pinned Babel parser dependencies.
Local validation: 649 tests passed, 31 optional checks skipped; 14 native development checks passed on each exercised DSH version; authenticated headless-browser and Apple VM checks passed. Two fresh development trials produced working plugins, including a follow-up maintenance change. These observations do not guarantee arbitrary generated projects are correct.
Release CI: all 18 jobs passed on the tagged revision, including native development on Windows, macOS and Ubuntu.
Ordinary development covers DSH 0.1.5-rc.2. The 0.1.6-alpha.1 lane is advisory; audited isolated-execution lanes remain 0.1.1-rc.2 and advisory 0.1.2-alpha.3.
Known upstream Web limitation: on DSH 0.1.5-rc.2, commands in an otherwise empty session may execute while their results remain hidden. Run the built-in /goal once to show the conversation; results remain intact. This workaround was checked through actual Chrome Computer Use without a model call. A separate startup-failure test intermittently timed out in alpha macOS CI; its cause remains unresolved, and that lane is advisory. Failed plugins were never announced ready.
Install into DSH Web:
dsh plugin --profile web add 'github:builtin-pb/dsh-developer#v0.1.1' --ignore-scriptsThe public v0.1.1 Git tag was installed into a fresh DSH 0.1.5-rc.2 Web profile with scripts disabled; both native knowledge cases passed and the profile was removed. No model request was made.
Restart DSH after installation. The archive and SHA256SUMS below provide the same ready-to-load plugin; no build scripts are needed.
dsh-developer v0.1.0
The first release of dsh-developer: one native workflow for building DSH plugins and working on the harness itself.
Included
- Project and toolchain inspection, package-script execution, and navigation into the exact installed DSH declarations or an upstream checkout.
- Packed-plugin installation and native tool verification in disposable profiles.
- Web development with owned server lifetime, native authentication, and an optional isolated browser route configured through
ui-setup. - Session diagnostics, static package checks, profile preflight and upgrade comparisons on the documented audit lanes.
- Optional isolated Build/Apply with reviewed provider admission, exclusive file publication and preserved recovery state when cleanup or rollback cannot be verified.
- One shared development skill for DSH and Codex, with native tool and Web examples.
Install
dsh plugin --profile web add 'github:builtin-pb/dsh-developer#v0.1.0' --ignore-scriptsRestart DSH Web after installation. Alternatively, download dsh-developer-0.1.0.tgz below and pass its local path to the same command. SHA256SUMS records the archive digest.
Requires Node.js ^22.18.0 || >=24.11.0. See the installation guide for setup.
Tested scope
All 15 cross-platform CI jobs passed. Release preparation passed 603 local tests, four real Mac VM checks, and both complete native DSH development suites. The release archive passed native verification and release/preview lifecycle checks.
Native development CI covers Windows, macOS and Linux with DSH 0.1.1-rc.2 and 0.1.5-rc.2. Audits and isolated Build have separate reviewed-runtime and provider requirements; current-runtime development support does not imply isolated execution support. The platform guide describes those boundaries.
Static analysis can report incomplete coverage for valid implementations. Such findings remain explicit; installation and passing tests do not establish correctness of arbitrary agent-generated code. Rendered browser checks were observed on macOS; rendered Windows browser automation remains outside that evidence.