User-facing changes to yothere, newest first. Versions follow semver. Install or upgrade with pip install --upgrade yothere.
1.5.2 (2026-07-04)
- First public PyPI release.
pip install yotherenow installs straight from PyPI. Earlier builds shipped as GitHub release wheels; publishing now runs through PyPI trusted publishing. - Private-data scrub. Shipped code comments and prompts were genericized so the public package carries no personal data.
- Installable PWA with web push. Add yothere to your phone’s home screen and receive a web push when a thread needs you, a notification path that does not depend on Telegram.
- Hardened hosted mode. Signup rate-limiting, a work-directory TCC guard that refuses macOS paths a background worker cannot read, and an env/cookie naming cleanup for multi-tenant deploys.
1.5.1 (2026-07-03)
- Rename from Relay to yothere is complete. The package, module, CLI command, and PyPI distribution are all
yothere.yothereis the canonical command andrelaystays as a deprecated alias, so old scripts keep working. The default home is now~/.yothere(an existing~/.relayis still honored as a fallback).YOTHERE_*is the going-forward environment namespace, and every legacyRELAY_*name still resolves. - Version integrity fixed. The installed package now self-reports the same version as its release tag; an earlier wheel mis-reported its version.
- Zero-key first run.
yothere initcreates the home layout and detects an existing brain, andyothere init --demodrives one thread end to end (blocked to reply to done) with no API key. - Safer worker default. Local Claude worker turns now run under a permission bypass contained by a send-gate that denies outward sends (mail,
git push, HTTP requests with a body, MCP send tools) while leaving plain reads allowed. You can opt out in configuration.
Note Earlier history predates the public rename (the "Relay" era, versions 1.0.0 through the 1.5.x line: the standalone package extraction, the Brain Protocol v1 client, the hosted multi-tenant cockpit, and the MCP surface). The full internal changelog lives in the product repository, which is private during the beta.