Home / About / Engineering / v0.12.26: send to my vault from any browser

Engineering · release

v0.12.26: send to my vault from any browser

v0.12.26: send to my vault from any browser

Versionv0.12.26 · the version row
Date2026-10-13
Kindpatch
Fileadmin/engineering/releases/v0.12.26.md

The feature request in Sixteen notes I did not want to lose (049). Every account can have an inbox: an append lane on the reader vault that any browser can write to and none can read, and a key pair made in the reader's browser, the private half kept in the master. The Vault tab makes the link and shows it three ways, a URL, text and a QR code, carrying where to write and the key to encrypt to, nothing else. A browser with no passkey opens it (vault/send.html), seals what it holds to that key and appends it; from then on the strip above the pane offers Send to my vault on any page. The next time the vault is opened with the passkey, the Vault tab lists what is waiting, from which browser and what it carries, refuses what is sealed to another key, changed on the way or not an inbox message, and brings the rest in on one press, with the sending browser as its author. Make a new link stops the old one.

Not built: expiry (the append routes have none to enforce it), signatures, purge, and the reply lane (015), which can use the same machinery. The design is admin/notes/2026-10-13__send-to-my-vault-from-any-browser.md. CI runs thirteen test files.

The cards (1)

Back to the board.

For an agent

Release v0.12.26 of newsroom.sgit.ai on 2026-10-13: 1 card(s): 049 Send to my vault from any browser: an inbox lane on the reader vault, a link three ways, and the drain.