ConnectOnionRelease Channels
Stable releases, exact-pin candidates, and opt-in previews stay explicit.
Current stable
v1.8.4
Installed by normal pip commands.
Release candidate
No active candidate
No active release candidate.
Latest preview
No newer preview
No newer feature-train preview is currently published.
Stable 1.8.4
Explicit configuration with co env, reviewed Gmail operations, verified Synology sharing and Outlook calendar commands are available on the stable channel.
The combined suite passed 8,666 tests and 11 installed-wheel checks. Real Gmail/Drive and one NAS were exercised. Microsoft contracts have mocked coverage; no live Microsoft tenant was tested. Companion hosting remains a separate deployment.
Read the 1.8.4 release · co env · Synology · OutlookStable 1.7 design
A Work Room is a client, not a status panel
OIP gives the browser one session boundary while native Codex and Claude Code keep their own conversation, lifecycle, permissions, and follow-up semantics.
A version is a compatibility promise, not a progress counter.
A version such as 1.6.3 maintains stable 1.6. New 1.7 features are tested as 1.7.0aN, 1.7.0bN, and 1.7.0rcN before 1.7.0 becomes stable.
Alpha
X.Y.ZaNIncomplete, usable slices for opt-in developers. Interfaces may still change.
Beta
X.Y.ZbNFeature-complete. Testing shifts to integration, upgrades, compatibility, and real users.
Release candidate
X.Y.ZrcNCould become stable unchanged. Only release-blocking fixes are accepted.
Stable / LTS
X.Y.ZDefault for normal installs. Preview builds require an explicit opt-in.
Install stable
Normal installs and upgrades ignore preview releases. Publishing a preview does not move existing users off stable.
Install exact stable
Use the exact pin for a reproducible stable installation. A broad --pre upgrade follows the highest published feature train, which is currently not published, rather than the stable channel.
Join the preview track
The --pre flag is the explicit opt-in. An exact pin such as connectonion==X.Y.ZaN also opts in and does not need --pre. No preview is published, so this command currently keeps the latest stable release.
Earlier preview 1.8.0a8: retained chat synchronization
The experimental OIP session-sync/0.1 extension exposes owner-scoped, revision-based chat history from the Agent machine. Clients can discover changes, read snapshots, and rename or archive chats without taking over another device's live connection. Drafts remain local, and an empty CONNECT does not appear as a chat.
Pair connectonion==1.8.0a8 with @connectonion/react@0.4.4-rc.1. Fresh signed CONNECT nonces prevent same-second replay collisions; Host relay metadata stays separate from resume state. Remote-only transcripts use SESSION_GET/ SESSION_SNAPSHOT. The paired O Chat PR tracks the frontend rollout separately.
The a6 and a7 tags were stopped before PyPI publication and remain immutable audit records. A8 includes the release-workflow repair and the empty-session correction found by live two-device E2E. Read the a8 release notes.
Current plan
1.6.x: previous stable maintenance line.
1.7.x: earlier maintenance line.
1.8.x: current stable line; 1.8.4 is the latest stable release.
Track the live scope in the 1.8.4 release tracker and the exact PR inventory and phase gates in cross-repository roadmap.
How a candidate earns promotion
Each release gate starts from the exact published package, launches its real co ai Host, and connects the production O Chat build through a real browser. The acceptance flow exercises a deterministic catalog search and attachment download through co browser, C, C++, and Rust projects, native Codex delegation, permission modes, cancellation, Host restart, and reconnect without resending the last prompt.
The run produces screenshots, sanitized logs, and a hash-addressed manifest. UI text alone cannot mark the gate as passed: process state, workspace output, reconnect state, and the absence of a duplicate input are checked independently. A failed gate stays failed and feeds the next issue and PR.
Backend promotion also collects the complete mocked oo-api test tree. Integration and live-provider cases stay explicit, but a new billing or API contract test cannot sit outside CI just because it was added in a separate test module.
Stable outcome: the accepted RC12 product source completed the exact installed-artifact gate and became 1.7.0. The coordinated browser reader is @connectonion/react@0.4.3; O Chat owns presentation rather than parsing provider-private streams.
Claude Code and Codex preserve their provider session IDs, stream normalized tool activity through OIP, and appear as live cards in O Chat through @connectonion/react.
The public wheel denied an outside-workspace write in headless Auto and left its target absent; explicit bounded Full access then completed the outside canary read and write plus the full Todo lifecycle.
A running coding task now streams compact, correlated provider activity and its nested approval into one Work Room. That Work Room remains a real remote Codex or Claude Code client: attributed user and provider messages and the provider-targeted composer stay visible through running, approval, Stop, reconnect, and completion. Temporarily unavailable input is disabled with a reason, not removed. Recent semantic steps stay readable; raw commands and outputs are opt-in details.
Descriptor-less OIP 0.1 peers remain readable through 1.7.x. Unsupported versions fail once without reconnecting, and privacy-safe compatibility telemetry contains no prompts, identities, or paths.
Design Journal
Why the preview train uses alpha, beta, and RC
Release notes explain what changed. The design journal explains why OIP owns the browser boundary, while a Work Room treats one long native coding task as a live, correlated surface rather than a terminal transcript.
Read the Work Room decision