·
16 commits
to main
since this release
cosyncing client downloads
These are broker-independent Flutter clients. Install and run the broker first,
then use cosy pair to authorize the client.
What's new in 0.3.0
- Secondary Codex and Pi clients can join the broker's current Drive owner
without starting another native Resume. - Session ownership is kept separate from each client's mutation authority;
stale ownership revisions and concurrent handoffs fail closed. - Background Observe connections remain read-only. Claude Code's secondary-client
behavior and OpenCode's shared-live behavior are unchanged. - Setup, repair, doctor, and uninstall share one receipt-based Pi bridge ownership
decision. A stale bridge updates automatically only when its receipt and current
contents prove that cosyncing owns it; user edits and unsafe targets remain
protected.
Known issue
Codex transcript events can still appear slightly out of order in some
multi-client sessions. This release does not claim to resolve that separate
ordering and compare-and-swap investigation.
Downloads
- Android:
cosyncing-client-*-android.apkis signed with cosyncing's
long-lived Android release key. Sideloading requires permission to install
apps from the browser or file manager you use. Keep the same signing key for
every update; Android refuses an update signed by a different key. - Linux x64: extract
cosyncing-client-*-linux-x64.tar.gz, keep the bundle
together, and runcosyncing. GTK 3, WebKitGTK 4.1, libsoup 3, and libsecret
must be available on the host. - macOS Apple Silicon: the DMG is intentionally not Developer ID signed or
notarized. Drag Cosyncing to Applications, then Control-click it and choose
Open on first launch. Only continue if you trust this repository and the
published checksum. - Windows x64: extract the complete ZIP before running
cosyncing.exe.
The build is intentionally unsigned and may show a Microsoft Defender
SmartScreen warning. Choose More info → Run anyway only if you trust this
repository and the published checksum.
iOS is not distributed in this release. TestFlight and App Store distribution
require an active Apple Developer Program membership. The iOS source and
simulator build remain covered by CI.
SHA256SUMS detects download corruption or replacement; it does not establish
a trusted publisher identity for the unsigned macOS and Windows builds.