Skip to content

Releases: compressius/cmx

CMX v0.1.42-nightly.20260916210810.64dbc63135b7

Choose a tag to compare

Experimental CMX nightly built from private source revision 64dbc63135b7. Verify downloads with SHA256SUMS.

Added

  • CMX can now run locally without a CMX account. The TUI offers a Continue
    locally path, while optional sign-in unlocks detailed usage statistics and
    the account dashboard.

Changed

  • The landing page and downloads now distinguish account-free local use from
    the optional dashboard sign-in path. Unsigned installations send only
    anonymous aggregate metrics, isolated from account dashboards.
  • Compression policy 2 now evaluates full bounded internal-call costs, keeps
    unknown pricing distinct from zero, and records local known/UNKNOWN monetary
    decision aggregates.
  • Durable summary reuse now requires matching policy and validator metadata
    plus structural source validation; legacy numeric tail preservation is no
    longer an effective policy-2 gate.

Fixed

  • Persist optional-use-mode upgrades independently of compression-policy upgrades,
    preserving existing tuning and unknown configuration fields.
  • Cancel optional TUI pairing work and ignore stale results; report sign-out
    failures and refresh running gateway state on account transitions.
  • Enforce the anonymous metric endpoint's 8 KiB limit while reading UTF-8 bytes
    and reject impossible calendar dates.
  • Upgraded SQLite databases can be reopened by the pinned baseline binary
    without refusing the forward migration or discarding durable metadata.
  • Net saved-token counters are floored at zero, so internal accounting cannot
    present negative compression savings on a fresh installation.
  • Routine bounded compression stops no longer surface as alarming
    resource_limit or deadline statuses in public headers and gateway status;
    the detailed reason remains in local audit data.

CMX v0.1.41

Choose a tag to compare

@administrakt0r administrakt0r released this 16 Sep 16:21

CMX v0.1.41

CMX can now be used locally without creating or signing in to a CMX account.
Account sign-in remains available when you want detailed usage statistics and
the CMX dashboard.

  • The TUI offers Continue locally alongside the optional sign-in path.
  • cmx setup works for local use without a CMX account and keeps native
    provider sign-in separate from CMX account sign-in.
  • Local installations send only bounded anonymous aggregate metrics; they are
    isolated from account devices and never appear in account dashboards.
  • The website and downloads now clearly separate account-free installation
    from the optional dashboard sign-in path.
  • Compression policy and local database upgrade reliability improvements from
    the current release line are included.

CMX v0.1.41-nightly.20260916155722.23450e10b699

Choose a tag to compare

Experimental CMX nightly built from private source revision 23450e10b699. Verify downloads with SHA256SUMS.

Added

  • CMX can now run locally without a CMX account. The TUI offers a Continue
    locally path, while optional sign-in unlocks detailed usage statistics and
    the account dashboard.

Changed

  • The landing page and downloads now distinguish account-free local use from
    the optional dashboard sign-in path. Unsigned installations send only
    anonymous aggregate metrics, isolated from account dashboards.

Changed

  • Compression policy 2 now evaluates full bounded internal-call costs, keeps
    unknown pricing distinct from zero, and records local known/UNKNOWN monetary
    decision aggregates.
  • Durable summary reuse now requires matching policy and validator metadata
    plus structural source validation; legacy numeric tail preservation is no
    longer an effective policy-2 gate.

Fixed

  • Upgraded SQLite databases can be reopened by the pinned baseline binary
    without refusing the forward migration or discarding durable metadata.
  • Net saved-token counters are floored at zero, so internal accounting cannot
    present negative compression savings on a fresh installation.
  • Routine bounded compression stops no longer surface as alarming
    resource_limit or deadline statuses in public headers and gateway status;
    the detailed reason remains in local audit data.

CMX v0.1.40-nightly.20260916120858.5995d520d679

Choose a tag to compare

Experimental CMX nightly built from private source revision 5995d520d679. Verify downloads with SHA256SUMS.

Changed

  • Compression policy 2 now evaluates full bounded internal-call costs, keeps
    unknown pricing distinct from zero, and records local known/UNKNOWN monetary
    decision aggregates.
  • Durable summary reuse now requires matching policy and validator metadata
    plus structural source validation; legacy numeric tail preservation is no
    longer an effective policy-2 gate.

Fixed

  • Upgraded SQLite databases can be reopened by the pinned baseline binary
    without refusing the forward migration or discarding durable metadata.
  • Net saved-token counters are floored at zero, so internal accounting cannot
    present negative compression savings on a fresh installation.
  • Routine bounded compression stops no longer surface as alarming
    resource_limit or deadline statuses in public headers and gateway status;
    the detailed reason remains in local audit data.

CMX v0.1.39-nightly.20260916115627.c2146344e18d

Choose a tag to compare

Experimental CMX nightly built from private source revision c2146344e18d. Verify downloads with SHA256SUMS.

Changed

  • Compression policy 2 now evaluates full bounded internal-call costs, keeps
    unknown pricing distinct from zero, and records local known/UNKNOWN monetary
    decision aggregates.
  • Durable summary reuse now requires matching policy and validator metadata
    plus structural source validation; legacy numeric tail preservation is no
    longer an effective policy-2 gate.

Fixed

  • Upgraded SQLite databases can be reopened by the pinned baseline binary
    without refusing the forward migration or discarding durable metadata.

CMX v0.1.38

Choose a tag to compare

@administrakt0r administrakt0r released this 15 Sep 21:46

CMX v0.1.38

This release restores effective compression for upgraded installations and
repairs databases affected by incomplete historical audit migrations.

  • Compression starts at 1,000 estimated tokens with a 1,000-token recent tail,
    five rounds, no cooldown, and a 512-token summary limit.
  • Existing compression settings migrate once with an owner-only rollback copy;
    provider routing, protected tools, and later user changes remain intact.
  • Startup repairs missing compression request identifiers using a consistent
    SQLite backup without deleting usage, session, or compression history.
  • Responses JSON/SSE summaries, incomplete terminal events, bounded retries,
    and internal usage accounting are handled consistently.
  • Nudges retain the real compression result, and decision diagnostics remain
    content-free.
  • Cache reads remain separate from estimated compressor savings and net totals.

CMX v0.1.37

Choose a tag to compare

@administrakt0r administrakt0r released this 15 Sep 20:45

CMX v0.1.37

This hotfix repairs upgraded local databases that have a recorded audit
migration but are missing the request_audits table.

  • CMX restores the missing local-only audit table safely at startup.
  • Gateway status and the TUI no longer fail with no such table: request_audits.
  • Existing usage, sessions, compression data, and configuration are preserved.

CMX v0.1.36

Choose a tag to compare

@administrakt0r administrakt0r released this 15 Sep 19:35

CMX v0.1.36

This release makes aggressive compression obey its configured summary-output boundary even for providers that do not accept an output-token parameter.

  • Cached summaries are now scoped to the configured output budget, so tightening that setting does not reuse a summary produced under a looser policy.
  • Provider-reported over-budget summaries are rejected before they can replace request context; when no usage is reported, CMX uses a ceiling local estimate.
  • Compression continues to preserve protected tools, opaque content, signed data, and the recent conversation tail.

No configuration migration is required.

CMX v0.1.35-nightly.20260915191417.639bd068b380

Choose a tag to compare

Experimental CMX nightly built from private source revision 639bd068b380. Verify downloads with SHA256SUMS.

Changed

  • Native-model context nudges now run on every eligible request, with cooldown disabled by default for maximum compression throughput.
  • Compression summaries use unlimited internal spend by default while preserving protected tools, opaque data, signed content, and the recent tail.
  • Summary replacements now use a focused 1,024-token output budget, and compression status reports both tokens saved and the precise stop reason after successful rounds.
  • CONFIG now highlights provider connection state, preference toggles and action results in place, and uses a consistent back hint and frame styling.
  • The TUI usage panel now reports only the current session's tokens handled, estimated net savings and requests, with a dashboard call to action for overall stats and savings.

Fixed

  • cmx upgrade --install and the TUI update action now select the published installer for the configured channel, so nightly installs are no longer replaced by stable builds.
  • Update installation now downloads the published launcher before running it, so a failed download is reported instead of masked as success by a curl | sh pipeline.
  • The TUI update control shows the check/install outcome on the button itself (available, updated, failed, up to date) instead of only in the authenticated activity footer, uses plain text labels rather than partial box glyphs, and derives its click target from the rendered header layout.

CMX v0.1.34-nightly.20260915153104.fe1b15ae0636

Choose a tag to compare

Experimental CMX nightly built from private source revision fe1b15ae0636. Verify downloads with SHA256SUMS.

Changed

  • Native-model context nudges now run on every eligible request, with cooldown disabled by default for maximum compression throughput.
  • Compression summaries use unlimited internal spend by default while preserving protected tools, opaque data, signed content, and the recent tail.
  • Summary replacements now use a focused 1,024-token output budget, and compression status reports both tokens saved and the precise stop reason after successful rounds.