Skip to Content Skip to main content

Changelog

Markers along the way.

Concise notes from the published Waykeep releases, with the changes and migration steps that matter.

Follow GitHub Releases

Latest published release

5.5.1

A clean install, on every npm.

Version 5.5.1 clears the fresh-install dead end on npm 11.5 and newer, where blocked dependency scripts leave the native database binding unbuilt and the first run fails. waykeep doctor now names that exact state and prints the command that fixes it.

Fixed

  • waykeep doctor recognises the missing native binding instead of reporting a generic failure.
  • The printed fix names the packages that need install scripts, which npm's own suggestion leaves out.

Documented

  • The README and the install guide carry the flag directly under the install command.
  • Released as 5.5.0 plus this fix; the sync foundations stay on the development line until they ship whole.
Inspect the source entry

Release archive

The route behind the current marker.

Reverse-chronological notes derived from the repository changelog.

  1. 5.5.0

    The package took the Waykeep name.

    The published package, the repository, the marketplace plugins for both agents, and every display surface moved to one name. Local state, tool names, and environment variables kept working untouched.

    Added
    Project-identity migration after a rename or transfer with a privacy-safe dry run, and a contributor licence agreement gated on pull requests.
    Changed
    Package, repository, plugin, briefing, and export-header naming, with the previous binary kept as an alias.

    PackagingPluginsGovernance

    Read 5.5.0

  2. 5.4.0

    Imports, plugins, reports, and private scopes.

    Migration imports, marketplace plugins, install documentation, honest usage reporting, private-project controls, and the integration contract arrived together.

    Added
    Imports, plugins, report rollups, scope controls, contract surfaces, and client-neutral routes.
    Changed
    Statusline-only init, exact-content deduplication, and adapter-based client behavior.
    Fixed
    Shell-relay capture fallback and preservation of unrelated Codex hook trust.

    CoreCLIIntegrations

    Read 5.4.0

  3. 5.3.1

    The package story caught up with cross-agent memory.

    The npm metadata and README began with the shared Claude Code and Codex workflow, added per-agent provenance, and corrected the documented tool count.

    Changed
    Package metadata, README positioning, keywords, and tool-count documentation.

    DocsPackage

    Read 5.3.1

  4. 5.3.0

    Codex reached the same local memory path.

    Codex gained automatic hook and MCP wiring, doctor checks, file-aware patch learning, shared session briefings, provenance, and live outcome capture through the same local store.

    Added
    Codex wiring, diagnostics, patch targets, captured outcomes, agent framing, and per-memory client provenance.

    CoreCodexClaude Code

    Read 5.3.0

Starting fresh?

Take the current route.

Install the published package, use the docs to wire your agents, or inspect every release at the source.