Skip to content

Publish v1.53.0 - #3012

Merged
philcunliffe merged 1 commit into
masterfrom
codex/release-v1.53.0
Nov 17, 2026
Merged

philcunliffe merged 1 commit into
masterfrom
codex/release-v1.53.0

Conversation

@philcunliffe

Copy link
Copy Markdown
Contributor

Prepare HypAware v1.53.0. This release adds user-facing features since v1.52.0, so it uses a minor version bump.

Release highlights:

  • Replay every eligible client's retained history with hyp sync --history all, with one preview and confirmation and named destination organizations.
  • Read, fix, list, mark, and delete standalone recommendations that have no report.
  • Repair Codex saved provider identities with offline backups, find the ChatGPT-bundled CLI on macOS for cloud capture, and preserve failed or unknown tool outcomes.
  • Capture Droid and Mastra Code session token snapshots, and use indexed Crush project paths for capture policy.
  • Show capture confirmation, hosted recording grants, and processing-child crashes more accurately in status; retain local first-sync release audit evidence.
  • Tolerate unknown organization config keys on older clients, fix local-only ordered query results, compact cache tables with a large delete backlog, and avoid regex stack overflow on very long token runs.
  • Default Linear login to the shared HypAware OAuth app.

Validation:

  • All 21 release-checklist hermetic smokes passed locally.
  • npm install and its declaration build passed; npm pack --dry-run verified 1,418 files with binaries and generated types, with no logs, tarballs, or node_modules in the package.
  • npm outdated found no outdated development dependencies. Runtime dependencies are unchanged.
  • Full tests, typecheck, LangGraph integration checks, and LLP validation are assigned to required CI on this revision and its merge group.
  • CPU and memory review: the release diff changes only the package version; no CPU or memory concern.

The repository has no CHANGELOG.md. Manual installed-daemon acceptance on macOS and Linux remains follow-up information; the hermetic battery does not establish it. npm publication is left to the user after the final merged commit is verified and tagged.

@HypForge

Copy link
Copy Markdown
Contributor

Draft weekly release-notes block for v1.53.0 (HypForge orchestrator; for the release owner to merge into the next weekly file on hypaware.ai, or to ignore). Runtime dependencies are unchanged from v1.52.0, as this PR says: squirreling 0.17.9, icebird 0.9.9, hyparquet 1.33.0. Every docs change in this release already shows on hypaware.ai (the site built from 4b6eb3d at 00:38Z today), so none waits on a site deploy.

Draft block (paste into the next weekly file)

Client release: 1.53.0 (date set at publish). No query engine change: squirreling 0.17.9, icebird 0.9.9 and hyparquet 1.33.0, as in 1.52.0.

New

  • Sync all history: hyp sync --history all sends every client's retained AI-gateway history in one run (for example after a machine joins a different organization), after one plan that counts the rows per client and names the organization each destination sends to, and one confirmation, while skipping clients marked local-only, keeping privacy-withheld rows back, and refusing while the first-sync review window is open. 1.53.0 (hypaware#3008)
  • Factory Droid token usage: Droid sessions now record their lifetime token counts and Factory credits (credits, not dollars) on one usage row per session, read from the settings file Droid keeps beside each transcript and dated to the session's first message, with child sessions counted separately and linked to their parent. HypAware's hook bookkeeping now lives in its own state instead of Droid's hooks.json; re-run hyp attach droid while the daemon is running to move an existing setup. 1.53.0 (hypaware#2971)
  • Mastra Code token usage: Mastra Code threads now record their running token counts (input, output, cache reads, cache writes, reasoning and total) in the standard token columns on one usage row per thread, dated to the thread's start, which local queries and exports carry, although the HypAware Cloud usage dashboard does not count them yet. 1.53.0 (hypaware#2979)
  • Delete a recommendation by id: hyp report delete <rec-id> deletes a recommendation that was published on its own, and for one that is part of a report it deletes nothing and prints the hyp report delete <kind> <period> <id> command that removes the whole report. Until HypAware Cloud stores recommendations on their own, every recommendation is part of a report, so the command prints that form. 1.53.0 (hypaware#2990)
  • Org sharing: org admins can now limit what members read with "server": { "sharing": "org_owned" } or "none" in the org config. With org_owned, members read their own sessions plus those in repositories owned by a GitHub account linked to the organization; with none, only their own. Admins read every session. The default stays all. The setting does not cover the graph, OpenTelemetry data, usage totals, GitHub and Linear activity, or published reports. Cloud (hypaware-server#1713)

Improved

  • Cache maintenance: routine maintenance now rewrites a cache partition once deleted rows (for example from retention or a purge) reach a quarter of its records, so queries no longer slow down reading past rows that are already gone. 1.53.0 (hypaware#2973)
  • Daemon status: hyp daemon status now shows a crashes: line under the processing row when the background processing process has exited unexpectedly since the daemon started, with the count and the last exit code or signal and its time, and each such crash is logged as an error so it counts in the recent errors that hyp status --verbose reports, while deliberate stops and requested restarts are not counted. 1.53.0 (hypaware#2974)
  • Organization config: an enrolled machine now applies an organization config that contains top-level settings its HypAware version does not know, ignoring those settings and logging config.unknown_keys_ignored instead of rejecting the whole config, and a config it rejected before applying is tried again after 6 hours instead of waiting for the organization to change it. 1.53.0 (hypaware#2976)
  • First sync: when the first-sync review window on a newly enrolled machine is ended early, HypAware now keeps a local record of when it ended and what ended it (a recognized AI agent, your organization's setting, or unknown), shows it in hyp status, and writes the window's start, early end and expiry to daemon.log, as a record only, since it cannot show whether a person approved the upload. 1.53.0 (hypaware#3005)
  • Linear login: hyp linear login no longer needs you to register your own Linear app, because it now authorizes Hyparam's shared HypAware Local app by default (read-only scope, no client secret, token kept on your machine), and a client_id in the plugin config or LINEAR_CLIENT_ID still selects your own app. 1.53.0 (hypaware#2985)
  • Report dates: the HypAware report skill, which hyp report generate uses, now has the agent put a Time zone: line (UTC unless you ask for another zone) on every report page, use that zone for calendar dates, check the labels with a bundled script before saving, and leave a recommended action's outcome unknown until the system that owns that state confirms it is done. 1.53.0 (hypaware#3004)
  • Query skill: the hypaware-query skill now tells agents to search your recordings only when a task needs earlier conversation evidence, not for ordinary current-work requests such as a PR or a current failure, and leaves full report generation to the hypaware-report skill. 1.53.0 (hypaware#2988)
  • Standalone recommendations: hyp report get, hyp report fix and hyp report list --recommendations can read a recommendation stored on its own with no report around it, which HypAware Cloud will start doing in an upcoming server update, and the hyp report fix picker lists those last as "Standalone recommendations". 1.53.0 (hypaware#2989)
  • Auth tokens: every organization token now belongs to a person or a service account. Tokens with no owner can no longer be minted or used, and the token inventory drops the Legacy type and filter. Cloud (hypaware-server#1700, hypscope#522)

Fixed

Local SQL with ORDER BY and a LIMIT, run from a folder that syncs, no longer returns too few rows (sometimes none) when local-only rows would have sorted first, and on context-graph tables it no longer lets hidden local-only content decide which rows come back (1.53.0, hypaware#2977). Codex chats saved under HypAware's gateway capture can be reopened again in Codex 0.166.0 and later, because the upgraded daemon renames their saved provider once, after Codex is closed and after a full local backup in ~/.codex/hypaware-provider-repair that HypAware never deletes, and the new hyp codex repair command previews (--dry-run), applies, or undoes (--restore <backup-path>) the same repair by hand (1.53.0, hypaware#2978). Codex tool results now record a failure when their command or script reports one, and no outcome when the result does not say, instead of always reading as a success; rows captured before this release are not rewritten, so check an older Codex row marked success against its output before counting it (1.53.0, hypaware#3003). hyp status now shows Capture unconfirmed for a client whose recording it cannot confirm, with an Attention entry (and a hyp backfill codex --dry-run next step for Codex), instead of Recording and "No issues detected", and it now notes that only the sources selected in hyp setup are recorded (1.53.0, hypaware#2984). hyp status no longer shows ChatGPT Work or Codex Cloud as recording when your hosted connection did not grant that source; each one now reads "Not connected" unless its own grant allows it, and the hint to start recording points to hyp setup (1.53.0, hypaware#3002). On macOS, Codex Cloud capture now finds the Codex CLI bundled inside the ChatGPT app (in /Applications or ~/Applications), so scheduled collection under the daemon's LaunchAgent no longer fails and leaves hosted chats unrecorded on a Mac whose only Codex CLI is that bundled one (1.53.0, hypaware#2983). When Crush keeps a project's database outside the project (with CRUSH_DATA_DIR, --data-dir or data_directory), HypAware now files its sessions under the project path in Crush's own project index and applies that project's .hypignore and local-only markings, and a database it cannot tie to exactly one project, such as one shared by several projects, is no longer recorded and is reported as withheld in hyp status (1.53.0, hypaware#3000). HypAware no longer drops a whole batch of recorded rows when one value holds a key-like string several million characters long (after sk-, ghp_, Bearer, password= or a JWT's eyJ, for example); the value is masked and the batch is written, and what gets masked is unchanged (1.53.0, hypaware#2992). On Windows, a HypAware command no longer fails with a permission error (EPERM) when it meets a lock file that another HypAware process is still deleting; it now keeps retrying for up to 2 seconds per pending delete before giving up (1.53.0, hypaware#3006). Product usage on an organization's page no longer times out for a new organization: product telemetry reads now skip other organizations' data and days, events and columns the query does not need, and nothing about what is collected, kept or who can read it changed (Cloud, hypaware-server#1711).

Docs and test changes

Docs only: the reports guide says how to download a published report as a Markdown ZIP (hypaware#2986); PRIVACY.md says HypAware Cloud reads an organization's GitHub activity itself once an admin connects the Hyperparam GitHub App (hypaware#2995); the Claude Code Cloud guide covers automatic updates, and an environment made with the older helper needs a one-time edit of its Setup script (hypaware#2999); and the Crush, first-sync and hyp sync --history all pages follow their changes (hypaware#3007, hypaware#3009, hypaware#3010). Tests: the suite passes under bun (hypaware#2998), and five flaky tests are fixed (hypaware#3006).

Before tagging

@philcunliffe
philcunliffe added this pull request to the merge queue Nov 17, 2026
Merged via the queue into master with commit 19b2872 Nov 17, 2026
13 of 17 checks passed
@philcunliffe
philcunliffe deleted the codex/release-v1.53.0 branch November 17, 2026 03:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants