Skip to content

WebCodex v0.3.9

Latest
Latest

Choose a tag to compare

View all tags
@yyjeqhc yyjeqhc released this 26 Aug 14:10
· 142 commits to main since this release
v0.3.9
9210e9b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Highlights

  • Streamlined first-run onboarding and npm package discovery, including webcodex share --auth query-token as the temporary-share fallback for MCP clients without Bearer-token UI.
  • Expanded hosted and MCP connectivity with managed OAuth/connect paths and the local MCP gateway.
  • Matured Workflow Session collaboration: canonical work_on_project, handoff/message observation, edit/withdraw/resolve flows, context ACK continuity, and Runtime Console collaboration surfaces.
  • Improved Windows and Runner operations with lifecycle/bootstrap hardening, persistent execution, replacement readiness, SSH resource parity, and stronger readiness/status integrity.
  • Hardened Server operations and release delivery with graceful Linux listener continuity, systemd rollback/lifecycle fixes, multi-architecture Server images, recoverable clone-free bootstrap, and disposable Server-image readiness.
  • Improved long-running execution/recovery, ACP durability, bounded model-facing response economy, and release tooling.
  • Added native Intel macOS (darwin-x64) release validation alongside Apple Silicon, Linux x64/arm64, and Windows x64/arm64.

Compatibility and upgrade notes

  • runtime:read is observe-only for Workflow Sessions. Session post/resolve/complete/replace/withdraw/close operations require session:collaborate.
  • Direct shared-key and normal pairing/full-interactive paths include session:collaborate. Existing PATs carrying only runtime:read must be reissued if they modify Session collaboration state.
  • Existing OAuth clients do not automatically widen an omitted/legacy scope ceiling. Adding session:collaborate requires reauthorization; a real ceiling change revokes existing access/refresh tokens and outstanding authorization codes.
  • webcodex share --auth query-token uses a temporary /mcp?token=... URL; the complete URL is a sensitive temporary credential. It is distinct from the deprecated Runner WebSocket query-token compatibility path; first-party Runners use Authorization: Bearer.
  • Hosted Servers with an operator-provided shared key use webcodex connect. Fresh self-hosted Servers keep the bootstrap administrator token on the Server and enroll repository machines with a short-lived pairing code plus webcodex login.
  • v0.3.8 remains the frozen previous-stable wire/rolling-compatibility fixture used by v0.3.9 validation.

Known client/platform boundaries

  • Local one-command webcodex share remains a Linux/macOS path; Windows uses CLI + Runner against a remote Linux Server.
  • ChatGPT Developer Mode, custom MCP Apps, and write/modify actions depend on plan/workspace/administrator policy; WebCodex cannot enable capabilities the client does not grant.

Release validation

The immutable v0.3.9 tag points to 9210e9b0342517ba7af15b2078ee708d49f96724.

Pre-tag exact-source release readiness passed on GitHub Actions run 32970465330, including the canonical release contract, full package-sharded Rust suites, frontend checks, WebSocket/polling zero-config E2E, coding-loop compare eval, native release-profile validation for all six published platforms, and disposable amd64/arm64 Server-image validation.

The authoritative post-tag release build passed on run 32975180128. All six native archives were built from the immutable tag with one shared build identity, Linux x64/arm64 passed the glibc 2.17 ABI/dependency gates, Windows artifacts passed native npm installer smoke, and one same-run assembled bundle was verified before publication.

Assets 11
Loading