注册并分享邀请链接,可获得视频播放与邀请奖励。

Honcho
@honchodotdev
Own your memory, steer your agents.
加入 April 2025
41 正在关注    6.3K 粉丝
Honcho 3.6 is out. One self-hosted Honcho can now serve many customers, each kept separate from the others. Turn on MULTI_TENANT and every read and write is scoped to the tenant named in the caller's token, enforced by Postgres row-level security. Each tenant's vectors get their own namespace, and the deriver takes work from tenants in turn, so one customer's backlog never holds up another's. You can pause one tenant's processing and leave the rest running. Also in 3.6: 👉 Dream history: every dream is recorded, so you can see which conclusions it added, which it let go of, and how the profile read before and after 👉 Honcho keeps serving when Redis has a problem, reading straight from the database 👉 3.6.1 makes the upgrade migration non-blocking, so your current version keeps serving while it runs The release notes at have the rest, including what self-hosters should plan for before upgrading.
显示更多