Releases

Each Psycheros package has its own semver lineage. The four packages release independently; running versions can drift between them. Use the table below as the source of truth for “what’s the latest version of X?”

Package	Current version	Notes
psycheros The harness daemon — chat UI, persistent memory loop, tool registry.	v0.3.1	CHANGELOG · all releases
entity-core Identity + memory engine consumed by psycheros via MCP.	v0.2.1	CHANGELOG · all releases
entity-loom Wizard for extracting memories and knowledge graphs from past conversations.	v0.3.1	CHANGELOG · all releases
launcher Browser-based installer + runtime dashboard.	v0.2.1	CHANGELOG · all releases

How to read this page

The version numbers above are read from each package’s deno.json at site build time. The site rebuilds and re-deploys on every push to main, so the page reflects whatever was just released in the last release sweep.

Inside a running Psycheros, the chat-header chip, launcher dashboard, and /api/health JSON all surface the version the daemon was built with, which may differ from the latest tag for a few minutes during a release sweep or for the lifetime of a container that hasn’t been restarted after an upgrade.

Release process

Releases happen in sweeps — one ritual evaluates all four packages and cuts the tags that have moved. The canonical procedure lives in runbooks/psyops-curated-release.md (private), but the user-facing shape is:

• Each released tag carries a CHANGELOG entry as its GitHub release notes (auto-extracted from the per-package CHANGELOG.md).
• The four packages have independent semver lineages. A release sweep may bump some packages and leave others unchanged.
• Docker images on the psycheros package are tagged <semver> plus latest; the psycheros-staging image stream is push-driven and isn’t part of the public release surface.