Skip to content

session-peer v1.0.1

Latest
Latest

Choose a tag to compare

View all tags
@abruption abruption released this 25 Sep 01:42
v1.0.1
55168c3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

session-peer v1.0.1

This maintenance release follows v1.0.0. Local and SSH messaging remain available without third-party Python dependencies. The Relay, MCP, and Antigravity integrations retain their existing opt-in boundaries.

Changes

  • The POSIX installer respects separately managed Claude Code and Codex skill paths (#187); it does not replace an independently installed skill.
  • The KR snapshot helper requires an explicit execution flag, so help or invalid arguments cannot trigger a snapshot (#175).
  • Device authorization polling backs off on 429 and slow_down responses instead of exiting immediately (#174).
  • macOS and Linux Relay receivers can pin the Codex executable; failures before native delivery are classified as refused rather than an unknown post-delivery outcome (#171, #176).
  • Windows Claude discovery excludes exited or reused process IDs (#173), while Codex discovery distinguishes a live unsaved writer from a missing thread (#166).
  • Update checks can report an outdated or incompatible separately installed session-peer skill without silently changing it (#167).
  • Optional Relay diagnostics now timestamp receiver lifecycle events, correlate attempts, and record per-leg frame progress without message contents (#172, #197).
  • The Relay control accepts the added metrics counters. Dependabot version-update PR creation is disabled (#189).

Install

For an existing package-manager installation, use its normal upgrade command, such as pipx upgrade session-peer. For a new Unix or WSL paired-device installation with MCP, use pipx install 'session-peer[relay,mcp]==1.0.1'. A core-only installation remains dependency-free on Python 3.9+; Relay needs Unix or WSL and Python 3.11+.

Service-managed macOS and Linux receivers must expose the target Codex executable to the receiver process, or configure the new explicit executable option. Confirm the selected target with --dry-run before sending.

Known limits

  • The root cause and owner of intermittent Cloudflare-to-KR Relay stalls (#161) remain unconfirmed. Added diagnostics improve future investigation; they do not establish a network fix.
  • A submitted or queued message is not an ACK. Do not automatically resend after an unknown post-submission outcome.
  • Package publication does not guarantee hosted Relay or OAuth availability. The Antigravity bridge remains experimental.
Assets 2
Loading