Skip to content

Signet Stable Release v0.157.3

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 02 Aug 07:46
· 1716 commits to main since this release
v0.157.3
94c3075

Signet Stable Release v0.157.3

Today we’re promoting v0.157.3 to Signet’s stable channel.

This release train makes setup far more complete, unifies how Signet connects to AI providers, strengthens memory and embedding reliability, and removes the retired experimental Rust service path.

Since v0.147.1, Signet has shipped 241 commits across 698 changed files: 40,647 lines added and 171,756 lines removed. The large reduction mostly comes from retiring the Rust daemon and its duplicated compatibility code.

Range: v0.147.1..v0.157.3
Previous stable: v0.147.1
New stable: v0.157.3

A safer, more complete setup flow

signet setup has been rebuilt around a reviewable plan. Before it changes your machine, it shows the configuration it intends to apply.

Setup can now:

  • connect providers through OAuth sign-in or API keys;
  • select models from the shared provider catalog;
  • configure memory extraction and aggregate recall separately;
  • connect an Obsidian vault;
  • configure a remote Signet service through daemon.url;
  • set up multiple agents and background-memory behavior;
  • run from a file or JSON, perform a dry run, and work safely in non-interactive environments.

This release also fixes a number of setup failures: malformed remote URLs, invalid provider routes, incomplete model choices, OAuth flows that could exit early, and configurations that were accepted but could not run.

One provider foundation for setup and memory work

Signet now uses the pi-ai provider catalog and sign-in flow across setup and the daemon’s background work.

In practical terms, the provider and model you configure are much more likely to be the provider and model Signet actually uses for memory extraction and aggregate recall. Routing, status reporting, and missing-provider behavior have also been hardened.

More reliable memory search and processing

The embedding index—the part of Signet that helps it find related memories—has received substantial reliability work.

  • Embedding migrations no longer interrupt recall. Signet can update its embedding data while memory search remains available.
  • Safer repair and backfill. Mismatched embedding sizes, incomplete index coverage, and startup promotion no longer silently leave memory search in a misleading or broken state.
  • Recovered missed transcripts. The daemon can recover native transcripts that were not captured during normal processing. (#998)
  • Repair stalled summary work. Signet can find and repair dead summary-job backlogs instead of leaving them hidden in the queue. (#901, #936)
  • More predictable background work. Pausing Signet now stops background inference cleanly, and several SQLite and provider-routing edge cases have been fixed.

Stronger native installs and integrations

The native release path has been hardened across supported platforms.

Compiled builds now receive stronger smoke checks, connector assets are packaged more reliably, and native embedding initialization has been made more robust. Managed integrations are less likely to retain an old SIGNET_PATH after an update or workspace move.

This release also improves update and install behavior for Codex and OpenCode integrations, including stale runtime recovery and wrapper startup after a skipped post-install step.

A simpler runtime model

The experimental Rust daemon has been retired.

Signet previously carried two service implementations and a compatibility switch between them. This release removes the Rust binary download path, its shadow proxy, parity tooling, and the SIGNET_DAEMON_RUNTIME setting.

There is now one maintained native service path. Users who relied on the experimental Rust option should use the normal Signet install going forward.

Security and correctness fixes

  • Checkpoint files are now validated before Signet loads them.
  • Startup index promotion preserves existing memory embeddings.
  • Signet no longer reports full embedding coverage while known gaps remain.
  • Configuration errors and blocked memory routes are surfaced more clearly instead of appearing healthy.

Updating

npm install -g signetai

Or update an existing install:

signet update

Stable users will move from v0.147.1 to v0.157.3. Nightly users on signetai@next remain on the nightly channel; this promotion does not change that behavior.

For the complete version-by-version release ledger, see CHANGELOG.md.

Contributors

Thank you to the people who contributed code to this stable release:

Assets 34
Loading