cosyncing client downloads

These are broker-independent Flutter clients. Install and run the broker first,
then use cosy pair to authorize the client.

Update your client with this release

0.6.3 changes the app. Notifications, Settings, Agents & Quota and Android's
Back button are reworked, and reading or clearing a notification on one device
now carries to your other devices. Update the Server first if you use the quota
page: the reset credits shown under Codex and Claude Code need a 0.6.3 Server,
and behind Tokdash older than 2.6.3 the row stays empty. Everything else in this
client works against a Server it could already reach.

The broker contract stays at revision 28 and the compatibility window stays one
revision wide, so a native client from 0.5.13 or earlier can watch a 0.6.x
Server but cannot drive it: it cannot answer a permission request or send a
prompt. The web client needs nothing: it ships inside the broker package and
always matches it. A 0.4.1 or older client also sits below the minimum accepted
client contract, still revision 17, and stays read-only against current brokers.

What's new in 0.6.3

• The Notifications page is usable at any length. Notifications that need a
  response, unread completions and problems now dismiss from their row, Clear
  all clears the page in one tap with Undo, and only the rows on screen are
  drawn, so a long history no longer freezes it. Reading one device's
  notification marks it read on your other devices — security alerts excepted,
  which stay unread until read there — and notifications plus their system
  notifications clear themselves 24 hours after they last changed.
• Settings is one reading-width column of plain rows under bold headings. The
  remaining cards, outlines and tinted boxes are gone, chip and segmented
  choices are selects beside their label, and Display is a single page running
  from Appearance through Conversation to Session visibility and the legend.
  The server row at the bottom of the sidebar opens a switcher with Add server
  and Manage servers, and Settings → Servers drops the created and last-used
  dates.
• Agents & Quota lists runtimes as rows with a text Restart action and puts
  providers two to a row on wide screens. Every five-hour window reads "5-hour"
  whatever the provider calls it, shows what remains and when it resets, and
  stays neutral until it runs low. Below the windows, Codex and Claude Code show
  the reset credits they hold and when the soonest expires, in amber in its last
  two days.
• On Android, Back returns to the page Settings, Notifications or Connection was
  opened from instead of closing the app, and on Android 14 and later a dismissed
  "Staying connected for notifications" notification stays dismissed while the
  background connection keeps running.

The 0.6.0 features that need both ends of the wire, notifications with every
browser tab closed, per-type notification settings and cross-device read and
clear, still need a 0.6.0 or newer Server. 0.6.3 is one.

Downloads

• Android: cosyncing-client-*-android.apk is 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 run cosyncing. 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.

cosyncing client downloads

These are broker-independent Flutter clients. Install and run the broker first,
then use cosy pair to authorize the client.

Update your client with this release

0.6.2 fixes the Server, not the client. Two notification defects are closed on
the broker side: a Server holding a long notification history no longer stalls
for up to half a minute about once a minute, and turning notifications on in a
new browser no longer makes it record every retained notification that browser
would never show.

Nothing in the app behaves differently, so a 0.6.1 client can stay as it is.
Clients are rebuilt here so the Server can ship its matching desktop archives.
The broker contract stays at revision 28 and the compatibility window stays one
revision wide, so a native client from 0.5.13 or earlier can watch a 0.6.x
Server but cannot drive it: it cannot answer a permission request or send a
prompt. The web client needs nothing: it ships inside the broker package and
always matches it. A 0.4.1 or older client also sits below the minimum accepted
client contract, still revision 17, and stays read-only against current brokers.

What's new in 0.6.2

• A broker holding a long notification history stays responsive. It used to stop
  answering for up to half a minute about once a minute, and while it was out
  sessions showed Reconnecting or failed to load and every client, request and
  live stream waited. On a store of about 1,700 notifications one check fell
  from about 14 seconds to about 0.1 seconds.
• Turning notifications on in a new browser no longer makes the broker record,
  and write gigabytes to disk for, every retained notification that browser
  would never show. A browser is alerted only to what happens after it
  registers; a native app still receives an alert that was already under way
  when it registered.

The 0.6.0 features that need both ends of the wire, notifications with every
browser tab closed, per-type notification settings and cross-device read and
clear, still need a 0.6.0 or newer Server. 0.6.2 is one.

Downloads

• Android: cosyncing-client-*-android.apk is 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 run cosyncing. 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.

cosyncing client downloads

These are broker-independent Flutter clients. Install and run the broker first,
then use cosy pair to authorize the client.

Update your client with this release

0.6.1 is a client polish release. The usage views are quieter and stop
explaining themselves in footnotes, pending work has one name per kind, an
Android update offer can be set aside, and a session that finishes more than
once is listed once.

Update the client on every device you use before, or together with, the Server.
The broker contract stays at revision 28 and the compatibility window stays one
revision wide, so a native client from 0.5.13 or earlier can watch a 0.6.x
Server but cannot drive it: it cannot answer a permission request or send a
prompt. The web client needs nothing: it ships inside the broker package and
always matches it. A 0.4.1 or older client also sits below the minimum accepted
client contract, still revision 17, and stays read-only against current brokers.

What's new in 0.6.1

• Agents & Quota shows only quota windows, and token usage lives in the Usage
  overview. The overview's day view drops the day streak, peak day and weekday
  chart that a single day cannot fill, and the report, its project leaderboard
  and the workspace overview drop their explanatory footnotes; how agent time
  is estimated stays on its tooltip.
• Pending work has one name per kind on both the overview and Notifications:
  "Waiting for you" for questions and approvals, "Unread completions", and
  "Problems" for failed runs and security or server alerts. The "Needs
  attention" grouping is gone, so the same filter is no longer reachable under
  two names.
• On Android a new app release is offered once in a dialog with Later, instead
  of a banner that stayed over every screen and could not be dismissed. Setting
  it aside keeps the update in Settings → General, still carrying its update
  dot.
• On phones and other narrow screens, reopening the sidebar after opening a
  session from it keeps the projects and subagent groups you had open, instead
  of collapsing every project again.
• A session that finishes more than once is listed once in Notifications and in
  the overview's Unread completions: its newest outcome replaces the earlier
  ones, as it already did in the system notification center.

The 0.6.0 features that need both ends of the wire, notifications with every
browser tab closed, per-type notification settings and cross-device read and
clear, still need a 0.6.0 or newer Server. 0.6.1 is one.

Downloads

• Android: cosyncing-client-*-android.apk is 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 run cosyncing. 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.

cosyncing client downloads

These are broker-independent Flutter clients. Install and run the broker first,
then use cosy pair to authorize the client.

Update your client with this release

0.6.0 is the largest client release to date. Session tabs stay open beside an
overview, the sidebar follows you into Notifications and Settings, each
notification type is configured on its own, notifications reach a browser with
every tab closed, and reading back through a long session keeps its place.

Update the client on every device you use before, or together with, the Server.
This release ships broker contract revisions 27 and 28 together and the
compatibility window stays one revision wide, so a native client from 0.5.13 or
earlier can watch a 0.6.0 Server but cannot drive it: it cannot answer a
permission request or send a prompt. The web client needs nothing: it ships
inside the broker package and always matches it. A 0.4.1 or older client also
sits below the minimum accepted client contract, still revision 17, and stays
read-only against current brokers.

What's new in 0.6.0

• The workspace keeps session tabs visible, including a single open session,
  and adds an overview plus Close all with Undo. Closing a tab leaves that
  session running. Phones and other narrow screens open the same sidebar as a
  drawer from the menu button.
• The roster starts with every project collapsed and marks one that needs input
  or has finished work with a single dot. Rows use the harness's own logo and
  keep subagent hierarchy, with the parent's status and its descendants' cues
  shown separately.
• Conversations use a compact context header and composer, with model,
  permissions, microphone, context usage, Send and Stop within reach.
  Conversation text size, spacing and reading width persist on their own. Flat
  White Minimalist is the new default palette, with the new Quiet Workspace
  palette and bundled Lato typography.
• Notifications are configured per event type in three families: Sessions,
  Security and Server. On Android each type is its own system channel. Each
  event now notifies once instead of on a ladder of reminders, opening a
  session or tapping its notification clears it, and reading it on one device
  clears it on your other devices.
• Closing the window keeps Cosyncing running on macOS and Windows so
  notifications still arrive. Android has an off-by-default switch that stays
  connected in the background.
• Reading back through a long session no longer loses your place. The client
  holds up to 500 rows and about 4 MiB, unloads whole pages far from where you
  are reading, and restores exactly those rows. Following a reply as it streams
  in now draws almost every frame on time instead of dropping most of them.

For notifications with every browser tab closed, per-type notification settings
and cross-device read/clear, use a 0.6.0 client with a 0.6.0 broker release.

Downloads

• Android: cosyncing-client-*-android.apk is 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 run cosyncing. 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.

cosyncing client downloads

These are broker-independent Flutter clients. Install and run the broker first,
then use cosy pair to authorize the client.

Update your client with this release

0.5.13 corrects how a refused Codex takeover is explained. A session whose
Codex daemon ownership could not be verified no longer claims that Codex
Desktop may still control it; it reports the ownership check that failed,
which is a different problem with a different remedy.

0.5.13 keeps the minimum accepted client contract at revision 17, so a 0.5.0 or
0.5.1 client still drives a 0.5.13 broker. Codex background command cards
require a revision-26 client for safe reconnect reconciliation. A 0.4.1 or older
client remains read-only against current brokers.

Update the client on every device you use before, or together with, the broker.
The web client needs nothing: it ships inside the broker package and always
matches it.

What's new in 0.5.13

• A refused Codex takeover names its actual cause. When the daemon's ownership
  check could not be answered, the client says so instead of naming Codex
  Desktop or another client as a possible writer; a confirmed competing writer
  keeps the conflict wording. Applies to manual takeover and to automatic
  restoration, in all five locales.
• On the broker side of the same release, cosyncing doctor reads a Codex
  control socket that the runtime publishes as a symlink, and a managed Codex
  daemon is recognized on runtimes that append a --managed-daemon launch
  marker, so restarts stop refusing a daemon they already own.

For Codex background-command cards, use a 0.5.12 or newer native client with a
0.5.13 broker release. The web client ships with the matching broker.

Downloads

• Android: cosyncing-client-*-android.apk is 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 run cosyncing. 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.

cosyncing client downloads

These are broker-independent Flutter clients. Install and run the broker first,
then use cosy pair to authorize the client.

Update your client with this release

0.5.11 adds a live card for shell commands an agent runs in the background, and
lets Android share the usage image. An expanded live-state card now reports what
the underlying work is really doing.

0.5.11 keeps the minimum accepted client contract at revision 17, so a 0.5.0 or
0.5.1 client still drives a 0.5.11 broker. Those clients do not expose features
introduced by newer contract revisions; in particular an older client shows the
background-command card without its output preview. A 0.4.1 or older client
remains read-only against current brokers.

Update the client on every device you use before, or together with, the broker.
The web client needs nothing: it ships inside the broker package and always
matches it.

What's new in 0.5.11

• Shell commands an agent runs in the background appear as a live card in the
  session, showing the command, how long it has been running, the latest output
  lines, and how it ended — including a failure the session never mentioned.
  The card stays until dismissed, and a command that goes silent is withdrawn
  rather than left claiming to run.
• The shareable usage image can now be shared from Android, alongside desktop
  and the web UI.
• Usage rankings show the top five agents, models, and projects, and
  Settings → Agents shows each agent's logo. By agent lists every tool the
  machine reported.
• An expanded live-state card now shows its real state instead of always
  reporting "Running" with a clock that keeps climbing after the work finished.

For the background-command card with its output preview, use a 0.5.11 native
client with a 0.5.11 broker release.

Downloads

• Android: cosyncing-client-*-android.apk is 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 run cosyncing. 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.

cosyncing client downloads

These are broker-independent Flutter clients. Install and run the broker first,
then use cosy pair to authorize the client.

Update your client with this release

0.5.10 is a fix release. It repairs installer pairing on clients whose broker
is still starting, and restores the runtime controls that disappeared from
Settings → Agents when a managed runtime had nothing pending.

0.5.10 keeps the minimum accepted client contract at revision 17, so a 0.5.0 or
0.5.1 client still drives a 0.5.10 broker. Those clients do not expose features
introduced by newer contract revisions. A 0.4.1 or older client remains
read-only against current brokers.

Update the client on every device you use before, or together with, the broker.
The web client needs nothing: it ships inside the broker package and always
matches it.

What's fixed in 0.5.10

• Installer pairing holds its one-use claim while a newly started broker becomes
  responsive. Clients retry transient startup failures instead of dropping the
  offer and falling through to manual authentication.
• Settings → Agents no longer reports "Activity check unavailable" for a managed
  runtime that is already up to date.
• Force restart is offered on any server-managed runtime when nothing is
  pending. A wedged Codex daemon reports no pending change, which is exactly
  when the control used to disappear.

Use a 0.5.10 native client with a 0.5.10 broker release.

Downloads

• Android: cosyncing-client-*-android.apk is 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 run cosyncing. 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.

cosyncing client downloads

These are broker-independent Flutter clients. Install and run the broker first,
then use cosy pair to authorize the client.

Update your client with this release

0.5.9 makes the signed stable update channel visible across native clients.
Android can install a verified APK in-app; Linux, macOS, and Windows show their
installed version and open the matching accepted download in the browser.

0.5.9 keeps the minimum accepted client contract at revision 17, so a 0.5.0 or
0.5.1 client still drives a 0.5.9 broker. Those clients do not expose features
introduced by newer contract revisions. A 0.4.1 or older client remains
read-only against current brokers.

Update the client on every device you use before, or together with, the broker.
The web client needs nothing: it ships inside the broker package and always
matches it.

What's new in 0.5.9

• Native clients check the signed release channel without a broker connection,
  show their installed version under Settings → General, and mark Settings when
  an accepted update is available.
• Android authenticates and installs the verified APK after user confirmation;
  desktop clients open the exact accepted platform download in the browser.
• Linux clients verify that Secret Service can persist credentials before
  consuming an installer's one-use pairing. WSLg retries briefly while its
  keyring becomes ready and reports a recoverable setup error if it cannot.

For these features, use a 0.5.9 native client with a 0.5.9 broker release.

Downloads

• Android: cosyncing-client-*-android.apk is 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 run cosyncing. 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.

cosyncing client downloads

These are broker-independent Flutter clients. Install and run the broker first,
then use cosy pair to authorize the client.

Update your client with this release

0.5.8 adds a verified self-update flow for sideloaded Android clients. The app
checks the stable GitHub release channel at startup and, when a newer accepted
APK exists, can download it and open Android's installer.

0.5.8 keeps the minimum accepted client contract at revision 17, so a 0.5.0 or
0.5.1 client still drives a 0.5.8 broker. Those clients do not expose features
introduced by newer contract revisions. A 0.4.1 or older client remains
read-only against current brokers.

Update the client on every device you use before, or together with, the broker.
The web client needs nothing: it ships inside the broker package and always
matches it.

What's new in 0.5.8

• The Android client authenticates the release manifest, verifies the APK
  digest, application ID, version, and signing certificate, then asks Android
  to install it. Android still requires user confirmation and may require
  permission to install apps from Cosyncing.
• Other native clients retain their existing update behavior.

For these features, use a 0.5.8 Android client with a 0.5.8 broker release.

Downloads

• Android: cosyncing-client-*-android.apk is 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 run cosyncing. 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.

cosyncing client downloads

These are broker-independent Flutter clients. Install and run the broker first,
then use cosy pair to authorize the client.

Update your client with this release

0.5.7 reduces delays when opening and returning to active sessions. Update the
client before, or together with, the broker for the matching roster-refresh
behavior.

0.5.7 keeps the minimum accepted client contract at revision 17, so a 0.5.0 or
0.5.1 client still drives a 0.5.7 broker. Those clients do not expose features
introduced by newer contract revisions. A 0.4.1 or older client remains
read-only against current brokers.

Update the client on every device you use before, or together with, the broker.
The web client needs nothing: it ships inside the broker package and always
matches it.

What's new in 0.5.7

• Returning to a session refreshes its roster entry immediately instead of
  waiting for agent creation-readiness checks.
• Large Claude Observe histories yield during parsing and reuse recent parsed
  records as the transcript grows, keeping other broker and client work
  responsive.
• Agent startup readiness probes no longer hold up unrelated broker requests.

For these features, use a 0.5.7 client with a 0.5.7 broker.

Downloads

• Android: cosyncing-client-*-android.apk is 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 run cosyncing. 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.