Guppy 1.1.103: the claims ledger, on by default
New floors get the claims ledger with no setup, search sees a first claims sync while it runs, and replies no longer race the startup mail catch-up.

Guppy 1.1.103 is out. New floors get the claims ledger with no setup, search sees a first claims sync while it runs, and replies no longer race the startup mail catch-up.
What changed
- The claims ledger is on by default for new floors. A floor created on 1.1.103 builds its mail-cards index and its derived claims at first start, with no manual step, and keeps both current. If the floor's project folder is a git repo, its commits feed the ledger too. A plain folder works from mail alone.
memory get <key|card-id>returns the current value of a key or a card. After it come the competing values and the superseded ones, each with what replaced it.memory searchadds--exactand--newest, and the memory tools are also offered over MCP.- Agents start one fresh conversation after this install. Identity, memory, inbox and ledger are kept.
What we fixed
- A floor's first claims sync is searchable while it runs. It now applies whole claims in slices, so search sees the first slice within seconds, and a sync that stops part-way resumes where it left off.
- Replies sent during the startup mail catch-up are linked, not bounced. They are delivered as written and linked once the catch-up settles.
- The derived claims link commits, done mails and card status more carefully, including merge and cherry-pick commits and superseded cards. Accuracy validation is still in progress.
Upgrading
Floors made before 1.1.103 keep their settings. The first start after the upgrade can take longer on a floor with a lot of history while it indexes its mail. To roll back, reinstall 1.1.102.
Get it from the download page, or read the full release notes.