Repository navigation
DSCODE 0.7.54
DSCODE restores message submission in projects with prompt hooks and keeps IPv6 servers running after authenticated readiness succeeds.
Session hooks
The session-scoped hook adapter now supplies the working-directory service required by Harness 0.2.1-rc.3. Previously, a configured UserPromptSubmit hook could end the first turn with UNKNOWN: Cannot read properties of undefined (reading 'ensure'), before any model reply. The same missing service affected startup, tool and stop hooks. Hooks now receive the session's effective directory, including directory changes after creation.
The adapter injects and forwards only the services declared by the loaded hook bridge. Older Desktop runtimes therefore never access the newer working-directory service, while terminal runtimes receive it. Hook commands, blocking decisions and existing configuration remain in force; this change does not disable hooks or bypass a hook that rejects a message. Reload still does not repeat SessionStart.
IPv6 runtime connections
The HTTP carrier removes IPv6 URL brackets only when constructing Node's connection options. Runtime URLs and displayed addresses retain brackets. Both unary and streaming requests use the corrected address.
With dscode server --bind ::, the launcher can now reach its authenticated IPv6 loopback readiness endpoint. Previously, resolving [::1] as a hostname failed even while the Host was serving requests, and the launcher terminated that Host after 90 seconds. This fixes the false timeout; it does not change readiness deadlines, authentication, transport encryption or supervisor restart policies. See the remote runtime guide.
Validation
The original public 0.7.52 macOS ARM64 archive reproduced the hook error with a disposable project and deterministic model. Replacing only its hook adapter allowed the same turn to execute the hook and return a complete reply. Source integration passed shared-Host submission, concurrent creation, multiple clients, restart/resume, workspace instructions and reload with a prompt hook enabled.
All 1,357 unit/component tests passed. Carrier regressions cover IPv4, DNS names and IPv6 connection options, authenticated unary and streaming calls on ::1 and ::, and incorrect-token refusal. A real foreground CLI bound to :: stayed reachable with the same Host PID and launch ID for 95 seconds after readiness. Hook regressions cover all five supported hook points, effective-directory changes, prompt rejection and reload semantics. Lint and documentation checks passed.
The complete npm run check gate passed locally under Node 24.21.0: both TypeScript checks, 80.21% tracked-source line coverage, all 17 integration verifiers, package checks and 63 evaluation tests. The coverage inventory excludes the vendored TypeScript terminal, which is checked separately by type and component tests.
The Desktop tarball passed qualification against its pinned Harness 0.2.0-rc.2, including workspace hook isolation, one-time startup hooks, session restart, browser integration and native local installation. A regression case rejects service reads absent from the older bridge's dependency declaration. These checks do not establish rendered Desktop UI acceptance or live model inference.
The release workflow also gates publication on the full check suite and the exact standalone archives on macOS ARM64, Intel macOS, Linux x64 and Linux ARM64. A deployed Linux systemd restart loop, real provider inference, native macOS permission dialogs and every third-party hook command have no automated acceptance case in this change.