Cox v0.1.41

Seven upstream reliability improvements

• Preserve the recent history window when stored interrupt requests and large checkpoint lists compete for bounded-snapshot space. This fixes apparent history truncation without rewriting conversation data. Upstream #31266.
• Always classify stored provider-secret references as sensitive, including older entries with missing or false flags, and preserve the classification on save. Upstream #31403.
• Keep thread branch metadata synchronized with worktree branch changes, including shared and archived threads; ignore detached HEADs, stale events and threads that moved. Upstream #31599.
• Refresh pull-request divergence at turn completion even when background Git polling is paused. Upstream #31342.
• Avoid repeatedly reopening unreadable credential vaults on unrelated settings saves. Retry when vault configuration changes, a reference changes or secrets are explicitly refreshed; keep working instances and Cox model-service materialization intact. Upstream #31226.
• Include Pi sessions stored through an absolute --session-dir argument, including quoted/equals-form paths and instance-home expansion. Keep configured history directories and environment overrides. Upstream #30690.
• Allow snoozing existing unanswered questions without resolving or discarding them. Keep approvals visible, wake for new questions and answers, and retain Cox's asynchronous-question/Working-state distinction. Upstream #20058.

Side-chat permission inheritance, low-priority sidebar layout changes, native-mobile-only features and broad Effect refactors are deliberately excluded. The existing supervised first-turn side-chat policy is unchanged.

Validation

• Release commit: e3dc4ca64b37d70f727f447a50e242820259cafd.
• Local complete suites: 15,419 passed, 6 skipped — 5,655 Server, 5,092 Web, 3,363 shared packages, 1,237 client-runtime and 72 root/desktop tests.
• Full workspace typechecks, changed-file lint/format, production build, Go protocol tests and isolated runtime/development smoke checks passed.
• A fresh source-archive installation with frozen dependencies passed release version/commit checks and isolated runtime/development startup, authentication and HTTP/WebSocket origin checks.
• A fresh local npm-tarball installation passed repeatable runtime patching, native PTY, offline Cursor SDK prewarm and isolated runtime authentication/origin checks.
• No paid inference was started and no live application data was changed.
• All four release CI jobs passed: Core, Server, Web and Distribution. CI independently reproduced 15,419 passed, 6 skipped, including 5,655 Server and 5,092 Web tests.
• All three desktop jobs passed on macOS Apple Silicon, macOS Intel and Windows x64, including packaged backend/native PTY and app-window smoke checks. Both macOS jobs verified unpacked, ZIP and DMG application signatures and the bundled Node signature.
• npm publication succeeded through GitHub OIDC. Public version metadata and latest resolve to 0.1.41; the actual public tarball passed SHA1/SHA512, embedded version, licenses and six-platform protocol-bridge checks. Public SLSA provenance references the exact release commit and public tarball digest.
• The public npm package matches the publishing-workflow artifact byte-for-byte and passed a fresh isolated install, repeatable postinstall, native PTY, offline Cursor SDK and runtime/authentication/origin checks.
• Downloaded desktop workflow artifacts passed their SHA256 sidecars and installer/blockmap structure checks. Both macOS ZIPs contain the expected server version, bundled Node, UI, target protocol bridge and licenses, with other-platform bridges removed.
• All GitHub release assets were independently downloaded from public URLs. SHA256SUMS matches the tested manifest and verifies the source archive, desktop installers, ZIPs, blockmaps, sidecars and build manifests; every downloaded file matches its tested local/workflow artifact byte-for-byte.
• Cox checks
• Desktop packaging
• npm publishing

Install

npm install --global @doublepi123/cox@0.1.41

For the prebuilt source archive, extract it, run pnpm install --frozen-lockfile, then pnpm start.

Desktop packages use an embedded loopback backend and isolated ~/.cox/desktop state. macOS bundles use ad-hoc signatures, not Developer ID signing or Apple notarization; Windows installers are not publisher-signed. OS trust warnings may therefore still apply.

This release does not update or restart an existing local Cox deployment.