Skip to content

v0.3.1 — Reliability fixes and community contributions

Choose a tag to compare

@abruption abruption released this 05 Oct 04:34
6b48092

Retrospective GitHub release record added on 2026-10-05 (KST).
Original npm publication: 2026-10-04T14:32:10.826Z (UTC).

Fixes since 0.3.0

  • Preserve outcomes per host when SSH send responses are malformed; accept unnamed Claude PID targets with name:null for dry-run/send and JSON/text results (#95, #97).
  • Parse Codex sqlite_home with TOML semantics, including escaped root keys. Nested-only keys are not root overrides; inactive opt-in does not bypass the storage guard (#96).
  • Reject reserved Codex/nested-URI prefixes in Claude Reply-To routes and block unresolved nested URI transport at the wire receiver before SSH/queue execution (#101).
  • Bound Claude registry metadata reads; skip unsafe, oversized or invalid records while preserving healthy sessions, with POSIX FIFO/race coverage (#102).
  • Accept a verified numeric UID 0 writer identity and continue refusing missing/malformed/mismatched identities (#103).
  • Include the multi-host migration documentation correction missing from the 0.3.0 archive (#91).

New Contributors

Welcome and thank you to @rupayon123 for their first contributions to this repository:

  • #95: per-host SSH result isolation and nullable Claude target-name handling.
  • #96: TOML-aware Codex sqlite_home detection.

Compatibility and verification

SSH endpoints must both run 0.3.1. Existing Windows-client jump, deployment and update-notice validation limitations remain; no live-agent ACK or fleet upgrade is added by this patch.

Exact-source CI/CodeQL passed. The authenticated stage, Actions artifact, exact-source local pack and public package are byte-identical (190,315 bytes; SHA-256 ba8b85b03229bc99ca30d52251790d7e75b90551de924b99edce22570f7fa401). Provenance binds the source/workflow/run below; signature audit and fresh public installation/removal passed.

Published package and source

npm install --global --ignore-scripts session-peer@0.3.1

posted/queued report submission, not consumption or ACK. An unknown outcome is not safe to retry automatically.