Skip to content

v5.0.0

Choose a tag to compare

@github-actions github-actions released this 24 Oct 13:53
· 92 commits to main since this release

[5.0.0] - 2026-10-24

Changed

  • Standalone binaries are the recommended distribution, an explicit Bun package route is the secondary recommendation, and npm remains compatible with supported Node.js installations. Binary and npm users do not need to install Bun for harnessed itself; upstream tools keep their own runtime requirements.
  • The default README is English, with Simplified Chinese in README-zh.md and an English compatibility mirror. New commit descriptions and release records use English; historical records are unchanged.
  • Host spawners and the Claude Agent SDK load only when their execution path is selected. Metadata, first-party hooks, injected test spawners and Codex dispatch no longer eagerly initialize the external Claude SDK. Existing permissions, cancellation, state and error contracts are retained.

Fixed

  • One-line installers distinguish a successfully installed binary from a failed setup, preserve setup failure evidence, and show a retry command instead of success-only update guidance.
  • Setup includes failures of explicitly selected optional components in its final result, keeps optional counts separate from base configuration, and no longer prints a successful completion message when installation failed.
  • PowerShell installer executable strings stay ASCII so legacy Windows PowerShell ANSI decoding cannot turn UTF-8 punctuation into a closing quote and reject the shadow/setup instructions before execution.
  • Codex component teardown no longer inherits Claude commands or cleanup paths. Unknown inverse operations fail before execution; the reviewed global CLI exceptions and native resource operations retain separate safety policies.
  • Captured installation targets thread through native CLI/RPC, verification, state and backup paths rather than reselecting another host after planning. Native home overrides remain independent of harnessed state roots and shared Codex workflow skills.
  • Presence receipts do not authorize external updates or establish historical ownership. Explicit-context probes preserve existing receipt history, while unknown external update targets and disabled or unverified native components remain visible instead of being treated as ready.

Added

  • Explicit Bun first-party hook transport for Claude Code and Codex, including matching doctor, owned-artifact and teardown checks. Existing Node and binary hook command literals and consent boundaries remain unchanged.
  • update --package-manager bun selects Bun package updates explicitly; running a package on Bun does not establish which manager installed it. Compiled binary updates retain their own channel and reject package-manager overrides.
  • Reproducible runtime benchmark and controlled-PATH channel smoke scripts, including actual first-party hook behavior checks. Three-platform CI verifies Node/npm without Bun, standalone without external Node/Bun, and the optional Bun path without Node.
  • A shared immutable host installation context and pure effective component-plan resolver for Claude Code and Codex, retaining the existing seven installer methods and package channels.
  • Optional Codex uninstall declarations reuse the existing strict schema and command/path security screening; selecting a declaration is not authorization to remove unknown user content.
  • Bidirectional contracts compare harnessed workflow, command, agent-role and first-party hook payload declarations with production writer output, without replacing the existing hash ledger or backup policy.

Compatibility And Known Issues

  • No state/schema migration, automatic Bun installation or implicit package-manager switch is introduced. Choose one distribution; npm and standalone behavior remain supported.
  • Upstream gstack lease readiness remains blocked in the tested Windows Git Bash environment. This release does not change native symlink policy, bypass locking or replace an explicitly required upstream invocation with a static role review.
  • MCP registration is not authenticated execution evidence. API keys, host approvals and upstream runtime prerequisites remain separate from harnessed installation.