Skip to content

session-peer v1.0.0

Choose a tag to compare

@abruption abruption released this 24 Sep 02:50
dbe7f7b

session-peer v1.0.0

The first stable v1 release packages the runtime validated as RC4. The runtime
behavior is unchanged from v1.0.0-rc.4; this promotion updates the version and
documentation. Local and SSH messaging remain dependency-free in the core.
Optional MCP, paired direct/Relay messaging with end-to-end encryption, managed
admission, and the experimental Antigravity bridge remain explicitly opt-in.

Validation and changes

  • RC4 includes #162's sanitized per-attempt route diagnostics and one bounded
    pre-submission control/admission retry. An unknown post-submission outcome is
    never automatically resent.
  • #168 reduces normal-idle receiver reconnect gaps, uses 10/10-second Relay-leg
    keepalive, and exposes receiverRoleBusy/clientRoleBusy counters.
  • The five-host rc4-rerun-02 completed 14,436.65 seconds: public health 241/241,
    probes 147/147, submissions 21/21, and planned Relay restart recovery in
    3.182 seconds. Exact ACKs were 20/21. The original T120 Windows native Claude
    ACK is unconfirmed because its TUI closed. A separate, new one-shot check of
    the same path received an exact ACK; the user accepted this operational
    exception in #164. It does not retroactively change the original count.

Install

Use your existing package manager; do not mix installations or device identities.

# Unix / WSL paired transport and MCP
pipx install 'session-peer[relay,mcp]==1.0.0'
# Native Windows core and MCP (Relay receiver runs in WSL)
pipx install 'session-peer[mcp]==1.0.0'

The core supports Python 3.9+, MCP 3.10+, and Relay receiver/server Unix or WSL
3.11+. A macOS or Linux receiver started by launchd/systemd must have the target
TUI's codex executable directory on its service PATH (#171, #176); codexBin
is WSL-only. Check the same environment with send --dry-run. Relay device login
expires and may require reauthorization; #174 tracks 429/slow_down handling.

Boundaries

The source and owner of intermittent Cloudflare↔KR transport stalls in #161 are
not established. RC4's reconnect changes mitigate amplification, not the
underlying path. #161 remains open for v1.0.1 monitoring. Hosted Relay/OAuth
availability is operational and separate from package publication. Windows
session discovery can retain an exited Claude record (#173). The Antigravity
adapter remains experimental. A submitted or queued message is not proof of
consumption or ACK; never resend an outcome-unknown message automatically.