Syzygy 1.0.0: the first stable release

Syzygy 1.0.0 is the first stable release of the whole product. It turns copied material into a local history that you can search, preview, edit, tag, keep offline, and move between trusted devices. The desktop client, mobile companion, account surface, and server were brought to one stable contract for this release.

#What shipped

#A useful clipboard history

The stable clipboard workflow recognizes text, links, images, files, rich HTML, and document-like content. Each item keeps the information needed to decide what to do next: its type, title, source application when available, size, preview data, and local availability. A short text item can be copied again immediately; a large file can remain visible as metadata until you ask for the content.

Clipboard capture now treats keyboard events and direct paste as one workflow. The application preserves the original item when a derived edit or preview is created, so an edit does not silently replace the source you may still need.

#Preview before you paste

Preview surfaces open images, files, formatted text, and recognized document content without forcing you to leave the current task. Popup windows and the quick panel share the same item model, which keeps selection, preview, and paste actions consistent across entry points.

The preview layer also knows when content is only described locally and when its bytes are available. A pending file is not presented as a ready-to-copy file. That distinction prevents a half-downloaded item from reaching the system clipboard.

#Search and indexing

The indexer stores searchable text extracted from ordinary text, OCR results, and supported PDF content. Search can find an item by its visible text, filename, title, or recognized content. Index storage can be inspected and cleared from the application when you need to rebuild a collection.

#Tags, trash, and retention

Tags provide a lightweight way to group history without moving files into a new folder. Trash gives deleted items a recoverable state before permanent removal. Retention limits apply to history and trash together, while an item marked to remain offline stays on the current device until you remove it yourself.

#Trusted devices and private sync

Pairing establishes a relationship between devices before synchronization begins. The first catch-up exchanges small metadata headers, then transfers content according to the selected policy. Local paths are preferred when available; other encrypted paths can carry the same data when the devices are on different networks.

The receiver can learn that an item exists before downloading a large payload. This lets a phone show a new item without silently consuming its entire data plan. Sync state remains visible when a payload is waiting, transferring, or being verified.

#A stable account and activation foundation

The 1.0 line includes the first stable account, entitlement, and activation contracts used by the desktop and account surfaces. The server provides the backing service for device identity, pairing authorization, and account state.

The release also includes the first complete subscription and distribution path: platform downloads, account activation, device binding, and the server-side state needed to recover an account after a device changes. These pieces are intentionally part of the same release story. A clipboard item is useful on its own, but a multi-device product also needs a reliable way to identify the user, authorize a device, and explain its current access.

#A small example

Copying a PDF now follows a predictable path:

copy PDF
  -> capture title, size, and source metadata
  -> create a searchable text projection when possible
  -> show the item in history
  -> preview the original document
  -> optionally sync metadata to a trusted device
  -> download and verify the bytes when requested

The list stays useful during each step. You do not have to wait for a large file before searching or organizing the entry.

#Who should upgrade

1. Anyone replacing several clipboard utilities with one local history.
2. Teams that need a private bridge between a workstation and a phone.
3. People who search copied research, screenshots, and PDF excerpts later in the day.
4. Users who want deletion and retention to be explicit rather than hidden in a cloud dashboard.

This release establishes the behavior that later maintenance releases refine: local data remains understandable, device trust stays explicit, and background work does not take over the foreground interface.